Gitea
Connect gitea.com with a read-only access token and read repositories, commits, pull requests, issues, releases and Actions runs.
A Gitea connection reads gitea.com repositories with an access token that has
read permissions only. It calls only gitea.com. Self-hosted Gitea and
Forgejo servers are not supported yet. For the tables, columns and limits that
every forge shares, see the Git overview.
Preview
Git connections are in Preview and are enabled on request: contact
support@xentropy.ai. Until Gitea is enabled for your account it is not
offered in the forge selector, and its reads fail with PROVIDER_DISABLED.
Create a read-only token
Token permissions
The form lists these permissions with a copy button.
| Permission | Unlocks |
|---|---|
read:repository | Repositories, commits, pull requests, releases, tags, branches, contributors and Actions runs |
read:issue | Issues |
read:user | Who the token belongs to, for the connection test |
Set up the connection
Gitea connects with a token only; there is no sign-in button.
The repository list comes from Gitea's list of repositories your account owns. If a repository of an organization you belong to is missing, contact support@xentropy.ai.
Resources
| Resource | Available | Notes |
|---|---|---|
repositories | Yes | Repositories your account owns |
commits | Yes | The default branch, or the branch you choose, in the date range |
pull_requests | Yes | All states, filtered to the date range |
issues | Yes | Pull requests are left out |
releases | Yes | |
tags | Yes | |
branches | Yes | |
contributors | From commits | Gitea has no contributors list: commits in the date range, counted per author |
pipeline_runs | Yes | Gitea Actions runs; name is the workflow file, such as ci.yml |
Columns left empty
| Resource | Empty columns |
|---|---|
repositories | pushed_at |
commits | additions, deletions |
Commit line counts are left out so that commit reads stay fast.
Limits
Gitea pages hold at most 50 rows, so on the Free plan a read stops at about
5,000 rows. gitea.com sends no rate limit headers. If it answers 429, Xentropy
waits for Retry-After. See
Limits and refresh for pages, rows and
deadlines.
Errors
| Response | Code | Cause | What to do |
|---|---|---|---|
| 401 | PROVIDER_ACCESS_DENIED, stage auth | The token was deleted or mistyped | Generate a new token and choose Replace configuration |
| 403 | PROVIDER_ACCESS_DENIED, stage permissions | A permission is missing. details.missingScopes names it, for example read:issue | Generate a token with the permissions above; a token's permissions cannot be edited |
| 404 | NOT_FOUND | The repository does not exist, or the token cannot see it | Check the name and your access on gitea.com |
| Redirect | NOT_FOUND | The repository moved or was renamed | Select the repository under its new name |
| 429 | RATE_LIMITED | gitea.com is limiting requests | Retry after details.retryAt; scheduled refreshes wait by themselves |