Docs
Connections

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

On gitea.com, open Settings → Applications → Manage access tokens.
Name the token. Under Select permissions, choose Read for repository, issue and user. Leave the rest at No access.
Choose Generate token and copy it. Gitea shows it only once.

Token permissions

The form lists these permissions with a copy button.

PermissionUnlocks
read:repositoryRepositories, commits, pull requests, releases, tags, branches, contributors and Actions runs
read:issueIssues
read:userWho the token belongs to, for the connection test

Set up the connection

Open Connections, choose New connection, then Git, and choose Gitea.
Name the connection and paste the token.
Choose Test connection. The stages are Authentication (the token) and Repository access. The test lists the repositories the token can read.
Choose the repositories to allow, or none to allow every repository the token can read. Choose Save connection.
Open the connection, choose a resource, repositories and a date range, pick fields, preview 100 rows and save a dataset.

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

ResourceAvailableNotes
repositoriesYesRepositories your account owns
commitsYesThe default branch, or the branch you choose, in the date range
pull_requestsYesAll states, filtered to the date range
issuesYesPull requests are left out
releasesYes
tagsYes
branchesYes
contributorsFrom commitsGitea has no contributors list: commits in the date range, counted per author
pipeline_runsYesGitea Actions runs; name is the workflow file, such as ci.yml

Columns left empty

ResourceEmpty columns
repositoriespushed_at
commitsadditions, 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

ResponseCodeCauseWhat to do
401PROVIDER_ACCESS_DENIED, stage authThe token was deleted or mistypedGenerate a new token and choose Replace configuration
403PROVIDER_ACCESS_DENIED, stage permissionsA permission is missing. details.missingScopes names it, for example read:issueGenerate a token with the permissions above; a token's permissions cannot be edited
404NOT_FOUNDThe repository does not exist, or the token cannot see itCheck the name and your access on gitea.com
RedirectNOT_FOUNDThe repository moved or was renamedSelect the repository under its new name
429RATE_LIMITEDgitea.com is limiting requestsRetry after details.retryAt; scheduled refreshes wait by themselves

On this page