baseboard
All integrations

Source control

Gitea / Forgejo

See what each deploy contains, what a rollback would undo, open pull requests and whether CI passes.

What you see

  • Source control

    On the Deployments page as soon as Gitea / Forgejo is connected.

How to connect

  • Paste a key

    An access token with read:repository, from Settings › Applications. Works for Codeberg too. Get a key The key is checked against Gitea / Forgejo before it’s saved, then sealed so only the broker that calls Gitea / Forgejo can open it.
  • From a terminal

    The CLI asks for the same key at a hidden prompt, so an agent running it never sees the key.
    $ npx baseboard-cli connect gitea --project k57abc

Settings

Hostrequired
For example https://codeberg.org
Repositoryrequired
owner/name, as in the repository URL.For example acme/web

Connect Gitea / Forgejo and the rest of your stack in one place.

Free covers one project with three connections. Everyone starts read-only.