Kanban with git integration: git on the board

Tracker and code drift apart: the status on the board rarely matches the real state in the repository. Git on the board closes the gap — automatically.

How it works

Mention a card ID in a commit or branch name and the work links itself. The card shows a development panel with the branch, commits, pull request and build status. A marker on the board shows which cards have code.

Setup in a minute

Drop one script into your repository — done. It works with any git host. Alternatively, connect the repository webhook so pull requests move cards automatically.

Build & test status on the card

Report your CI results onto the card and read red, amber or green at a glance — without opening the pipeline.

Git-driven automations

Let the board react to your code: move a card when a branch appears, a commit lands, a pull request merges, or the build turns red.

Part of project management for developers. See also The Code Graph and Zuuna vs Jira.

Guides

• Link commits to cards automatically — the post-commit hook in five minutes.
• Connect GitHub pull requests to your board.
• Show build and test status on the card.
• Move cards automatically with git.
• Create an API token and make your first call.

The reference for this

How it works technically is open in the CLI reference — including the rule for when a card key means work and when it is only a reference. To build it yourself, use the REST API or webhooks.

Connecting the repository

How the connection is actually made is documented per provider: GitHub as an app install, Gitea even for an instance only reachable inside your network.