GitHub
Index repositories, issues, pull requests, and docs, with live retrieval for current state.
Status: Available · Last verified: 31 July 2026
GitHub is one of the connectors you can use today. It runs in both modes: content is indexed for semantic search, and some lookups go live to GitHub so you get current state rather than the last sync.
Connecting
In the web app, open Connections, click GitHub, and complete the GitHub OAuth flow. Remly requests read access; it does not request scopes to push code, merge, or administer repositories.
The connection is owned by the GitHub account that authorizes it. Remly sees what that account can see – connecting your personal account does not grant Remly access to an organization's private repositories unless that account already has it.
What gets indexed
- Repository documentation and text files, including READMEs and Markdown docs
- Issues, including bodies and comments
- Pull requests, including descriptions and review discussion
- Discussions
Binary artifacts, build outputs, and large generated files are not useful to index and are skipped.
What is fetched live
Some lookups query GitHub at request time instead of relying on the index, so results reflect current state – an issue closed a minute ago will not still read as open. Live results depend on GitHub's API being reachable and on your rate limit headroom.
Selection
You choose which repositories Remly covers. Narrowing the selection is the main lever you have over sync time and over how much noise reaches your search results. Changing the selection later cleans up content from repositories you removed.
Sync
GitHub supports real-time sync through webhooks, so pushes, new issues, and comments are picked up as they happen. Incremental syncs pick up anything the webhooks missed. You can also choose an hourly, six-hourly, daily, or manual schedule.
Permissions
Remly snapshots access at index time and filters results by your access at query time. Private repositories you cannot see are not indexed for you. If your GitHub access changes, the next sync refreshes the snapshot – there is a window between a permission change in GitHub and the next sync where results can reflect the older state.
Rate limits
Remly stays inside GitHub's per-account API rate limits and backs off on 429 and secondary rate-limit responses. On a very large selection, the first sync may take noticeably longer because of this.
When something goes wrong
| Symptom | What to do |
|---|---|
| Card shows Reconnect | The OAuth grant was revoked or expired. Reconnect from the Connections page. |
| A repository is missing from results | Confirm it is in your selection and that the authorizing GitHub account can see it. |
| Recent changes are not showing | Check the source's last sync time; run Sync now if webhooks were interrupted. |
| Sync is slow or stalled | Usually rate-limit backoff on a large selection. It resumes on its own. |
Disconnecting
Connections → GitHub → Disconnect revokes the grant and immediately and permanently deletes this connector's sources, documents, text chunks, embeddings, and permissions. Your account and every other connector are unaffected, and nothing in GitHub itself is touched. You can also revoke Remly from your GitHub account's application settings.
This is not the same as deleting your account, which follows a different path with a 30-day recovery window.
Plan requirement
GitHub is a cloud connector and requires the Full tier. See Plans and billing.