Feature
Connect GitHub to your Zuuna board
Commits, branches, pull requests and build status from GitHub land on the right card automatically. How to connect it — and what it does not do.
The GitHub integration links a repository to a group in Zuuna. After that, commits, branches, pull requests and build status appear on the card whose ID is mentioned in the commit message or branch name — with nobody linking anything by hand.
Setting it up
On the group's Code page you start “Connect GitHub”. That takes you to the install page for our GitHub App, where you choose which repositories it may access — that choice is yours, not ours. GitHub sends you back, the installation is recorded against the group, and you pick the repository. There is no token to copy: the app installation is the permission.
What happens automatically after that
Mention a card ID in a commit message or a branch name and the work links itself. Pull requests appear on the card with their status, and a failed build is visible on the board rather than only in the pipeline. The rules for that are in the tutorial on linking commits to cards automatically.
What it does not do
It does not sync GitHub Issues with Zuuna cards. The connection runs one way: what happens in the repository becomes visible on the board. Running both systems as issue trackers in parallel gives you two versions of the truth, and no integration fixes that.
Plan
Git on the board is part of the Developer plan, together with releases, the code graph, the REST API and webhooks.
FAQ
What permissions does the app get?
Only the ones you grant at install time for the repositories you select. You make that selection on GitHub's side and can change it, or remove the installation, whenever you want.
Does this work with GitHub Enterprise Server?
The app install flow targets GitHub.com. For a self-hosted instance inside your own network, GitLab and Gitea are the intended route — there you supply your instance address yourself.
Does every team member have to connect something?
No. The connection is between a repository and a group, not between a repository and a person. Once it is set up it applies to everyone working on the board.