Skip to main content
GitHub is where your engineering team’s work takes shape — in pull requests, issues, commit history, and code. Connecting GitHub to Knoq lets you ask natural language questions against all of that: find the PR that introduced a bug, summarize open issues blocking a release, or understand what changed in a module last week, without leaving the chat or switching context.

​
What Knoq can access

Knoq reads from your GitHub account using secure OAuth, scoped to repositories and organizations your account can access:
  • Issues — titles, descriptions, labels, assignees, comments, and status
  • Pull requests — diffs, review comments, CI status, and merge state
  • Commits and diffs — commit messages, authors, and code changes in accessible branches
  • Repository metadata — descriptions, topics, branch names, and contributor lists
  • Code search — searching the contents of files across accessible repositories
  • Organization and team metadata you have permission to view
Knoq queries GitHub in real time. Repository content is not indexed or stored — searches happen live against the GitHub API, so results always reflect the current state of your codebase.

​
What Knoq cannot access

  • Repositories you do not have at least read access to
  • Private repositories in organizations that have not authorized the OAuth app
  • Repository secrets, environment variables, or Actions workflow run logs beyond what the API exposes to your account
  • Resources outside the OAuth scopes granted during authorization

​
Connect GitHub

1

Open Settings → Integrations

In Knoq, click your avatar in the top-right corner, select Settings, then choose Integrations from the left sidebar.
2

Find the GitHub connector

Locate the GitHub card in the gallery. Use the Dev Tools category chip to filter the list.
3

Click Connect

Click the GitHub card and press Connect. Knoq redirects you to GitHub’s OAuth authorization page.
4

Authorize Knoq on GitHub

GitHub shows you the permissions Knoq is requesting. Review the scopes — they are read-only for most operations — then click Authorize. If your personal account belongs to a GitHub organization, you may also see an option to grant organization access (see Organization access below).
5

Return to Knoq

GitHub redirects you back to Settings → Integrations. The GitHub card shows a green Connected badge. Head to the chat and try your first GitHub query.

​
Example queries

Once GitHub is connected, ask Knoq questions like these in the chat:
Knoq reads the relevant GitHub data, synthesizes an answer, and links back to the specific issues, PRs, or commits it referenced.

​
Organization access

If your repositories live in a GitHub organization — rather than your personal account — you may need to explicitly grant Knoq access to that organization during the OAuth flow. On GitHub’s authorization screen, look for the Organization access section. Organizations you own will have a Grant button; organizations you’re a member of (but don’t own) will show a Request button. Click Request to send an approval request to your organization’s GitHub admin.
Organization admin approval is a GitHub platform requirement, not a Knoq limitation. If you need access urgently, ask your GitHub organization admin to approve the OAuth app in GitHub Organization Settings → Third-party access. Once approved, return to Settings → Integrations in Knoq and click Connect again — you won’t need to re-authorize from scratch, just repeat the flow to capture the updated org scope.
If your organization has an IP allowlist or enforces SAML single sign-on (SSO), you may also need to authorize the Knoq OAuth app for SSO access from within GitHub after completing the initial flow. GitHub will prompt you with a link to do this if required.

​
Permissions

Knoq requests read-only access to your GitHub repositories and metadata. It cannot make changes to your codebase or repository settings.
Knoq will never push code, merge pull requests, modify repository settings, or take any write action on your GitHub repositories or organizations. If you see unexpected repository activity, it is not originating from Knoq.