Feature
Connect Gitea or Forgejo to your Zuuna board
For your own Gitea or Forgejo instance: an address, a repository and a token used once and never stored — including instances with no route in from outside.
The Gitea integration links a repository on your own Gitea or Forgejo instance to a group in Zuuna. Because both projects exist to be self-hosted there is no central sign-in: you give the address of your instance, the owner and repository, and an access token.
Setting it up
On the group's Code page you enter the instance address, the owner and the repository, and supply an access token. Zuuna uses it to register the webhook directly in Gitea. The token is used once for that and then discarded — it is not stored.
Internal instances
If your instance runs only inside your network, Zuuna cannot reach it and the automatic setup fails. That is not a defect but the case it was built for: you are shown the URL and the secret and create the webhook in Gitea yourself. From then on your instance sends the events — the traffic runs outward, not inward.
After that
Commits, branches and pull requests land on the card whose ID appears in the commit message or branch name — the same mechanics as GitHub and GitLab, with your own instance behind it.
Plan
Git on the board is part of the Developer plan, together with releases, the code graph, the REST API and webhooks.
FAQ
Does Forgejo work the same way?
Yes. Forgejo is a fork of Gitea and speaks the same API, so the setup is identical.
Does my instance have to be reachable from the internet?
No. Only the automatic webhook setup needs reachability. Without it you create the webhook yourself using the URL and secret shown; your instance then sends the events.
What happens to the token?
It is used once for setup and not stored. If you revoke it in Gitea afterwards the connection keeps working — it hangs off the webhook, not the token.