Gitea, Forgejo & Codeberg
Gitea and its fork Forgejo run on a lot of small servers precisely because they ask for so little, and Codeberg runs Forgejo for everyone else. One connection covers all three: they share an API, so anything speaking it will work.
What you get
- Works with Gitea, Forgejo and Codeberg — one connection type for all three.
- Any host you can reach, including an instance on your own hardware.
- Connects with an access token you generate in your own settings.
- Mirror open issues onto a board and plan them alongside everything else.
- No administrator involvement — a personal token is enough.
One API, three names
Forgejo is a fork of Gitea and Codeberg is a public Forgejo instance, so all three answer the same API at /api/v1. Choosing Gitea in the connection dialog and entering your host is the right move for any of them.
Because the host is free-form, an instance running on a machine in your office is no different from a public one, as long as it is reachable.
Token scopes
Generate an access token with read:repository, write:issue and read:user. Reading covers the mirroring itself; write:issue is what allows the same token to create issues rather than only listing them.
Setting it up
Create an account, then find it under Settings → Integrations → Gitea. Every connection is part of the single Pro plan at $4.99 per month — there is no per-integration pricing and nothing here is an upgrade.
Questions
Is Forgejo supported separately from Gitea?
It doesn't need to be. Forgejo is a fork of Gitea and serves the same API, so the Gitea connection works against Forgejo and Codeberg unchanged.
Which scopes does the access token need?
read:repository, write:issue and read:user. The read scopes cover mirroring; write:issue lets the connection create issues as well as list them.
Can I use it with a private instance on my own server?
Yes, provided the instance is reachable from the internet. You enter the host when creating the connection, and the API is called at the standard /api/v1 path on it.