Issues & support
Set up Gitea / Forgejo
Connect your Gitea or Forgejo instance (Codeberg too — they share one API) to make issues and pull requests searchable — each becomes a document with its description and full comment thread, tied to its repository, author, assignees, labels and milestone, so “how did we fix X” answers from the closed issue. Read-only.
Before you start
- On the forge open Settings → Applications, name a token and grant it read access to repositories and issues — on current Gitea the read:repository and read:issue scopes, the same on Forgejo. Copy it right away; it's shown once.
- Only reads are ever issued; code, commits and diffs are never fetched.
- Documents → Gitea / Forgejo, enter Server URL — the address you open the forge on, including https:// (or https://codeberg.org) — and paste the Access token.
- Repositories: owner/name as the forge's URLs write it, one per line — or leave it blank and set Owner (org or user) instead.
- State: Open and closed, or Open only.
- Choose access groups, Test, then Sync.
| Owner (org or user) | Syncs everything an organisation or user has — private repositories included when the token can read them. Ignored whenever the Repositories list has entries; Test asks for one or the other if both are blank. |
|---|---|
| State | Open and closed (default) makes the history askable — “how did we fix X” lives in closed issues. Open only keeps just the live work, at the cost of that history. |
What comes in
- Each issue and pull request becomes a document titled owner/repo #number: title — state (open, closed, or merged for a pull request), author, assignees, labels, milestone, last-updated date and a link back to the forge, then the description and the comment thread — review comments included — each comment with who wrote it and when.
- Each repository also becomes a concept card with its description and its synced and open counts.
Access
Access is allow-only: the groups chosen on the source cover everything the forge brings in — the forge's own repository permissions are not mirrored.
Caps per sync: 200 repositories; per repository 3,000 issues, 3,000 pull requests and 5,000 comments of each kind, the most recent kept — Sync notes any cap it hits, and the rest are not synced. A repository with its issue tracker disabled, or one the token has lost access to, is skipped and noted rather than failing the whole sync, its existing documents kept; a listed repository that isn't found (renamed, or the token lost access) is noted and skipped. Test connects as the token's own user and says how many repositories it reached; it fails with a specific reason when the forge rejects the token or none of the listed repositories can be read. Revoke access any time by deleting the token under Settings → Applications on the forge.
Last updated 20 Sep 2026