On this page
Connect Gitea
Temps connects to Gitea and Forgejo (a hard fork of Gitea), whether you host them yourself or use Codeberg, the hosted service that runs Forgejo. You need a personal access token and the instance URL. Push events are verified with an HMAC signature, and the webhook is registered for you. Start from Connect a Git Provider if you haven't opened the Git Providers page yet.
Connect with a personal access token
- On the Add Git Provider screen, choose Gitea.
- Enter your Gitea Instance URL, e.g.
https://git.example.com. It must be HTTPS. - In Gitea, generate a token at Settings → Applications → Generate New Token with the
repositoryscope (read and write). Addissue(read and write) if you want preview comments on pull requests; Gitea posts them through its issues API. Copy the token. - Back in Temps, paste the token into the Token field and click Connect.
Gitea OAuth is not supported in this release — use a personal access token. Forgejo
and Codeberg work the same way; for Codeberg, the instance URL is
https://codeberg.org.
Your instance must be reachable over HTTPS — plaintext http:// is rejected so
your token is never sent in the clear. Put TLS in front of a self-hosted Gitea
before connecting it.
Once connected, confirm the status shows Active and continue with Confirm the connection.