Gitea

The Gitea provider covers gitea.com and self-hosted Gitea instances. It uses the same implementation as the Forgejo provider, so the Forgejo page applies here, apart from the default instance and the webhook headers. Refs from this provider have forge: 'gitea'.

Authentication

The provider accepts an access token:

import { gitea } from 'forges/gitea'

const forge = gitea({
  auth: { type: 'token', token: process.env.GITEA_TOKEN! },
}).create()

Without auth, the provider makes anonymous public reads.

Instance

The default instance is https://gitea.com. For a self-hosted instance, set baseUrl to the root of the instance. The provider appends /api/v1:

gitea({ baseUrl: 'https://gitea.example.com', auth })

refreshCapabilities() reads the instance version from /version.

Behaviour shared with Forgejo

These sections of the Forgejo page apply to Gitea:

• Marking notifications done
• Merging
• Reviews
• Checks and CI
• Changed files
• Search

Webhooks

Set webhookSecret to the secret configured on the hook:

const forge = gitea({
  webhookSecret: process.env.GITEA_WEBHOOK_SECRET,
}).create()

const events = await forge.webhooks.ingest({
  headers: request.headers,
  body: await request.text(),
})

Gitea sends these headers with each delivery:

The Gitea provider doesn't read X-Forgejo-* headers.

A label delivery doesn't say which labels were added or removed. A changed label set becomes a label event with the edited action, and removing every label becomes one with the unlabelled action.

Recording fixtures

GITEA_TOKEN=... FIXTURE_GITEA_REPO=owner/repo FIXTURE_GITEA_PULL=1 \
pnpm record-fixtures gitea

To add an issue, set FIXTURE_GITEA_ISSUE. To record a self-hosted instance, set GITEA_BASE_URL.

Capabilities

Generated by pnpm capability-matrix; do not edit by hand.