Apps in your repositories
Keep your team's apps as repositories on your code host: real history, merge requests and review. kanman's check gates every merge request, and a merge deploys.
Engineers want an app’s code where all their other code lives. Switch on Apps in repositories, and every app of the team gets its own repository on your GitLab or GitHub: clone it, branch, push, review it like anything else.
Switch it on
In Team > Budget and limits:
- Under What I may create (More options), allow New repositories. I create repositories only in your team’s own groups.
- Under Apps in repositories, turn on Keep apps in repositories.
- Optional: set a Group for app repositories, for example
acme/payments/apps. It must be one of your team’s groups. Left empty, I use your main repository’s group withapps/(GitLab) orapps-before the name (GitHub).
It is off by default. While it is off, apps live in kanman.
How changes flow
- My changes arrive as a merge request on a
kanman/app-branch. - Every merge request, mine or an engineer’s, gets my check as its commit status (
kanman/app-check) and a comment with what I found. - A merge into the default branch deploys the new version on your team’s runner.
- A revert rolls back, with the app’s data.
I never write to the default branch of an existing repository directly, and I scan everything I push for keys and tokens. Questions from my check are answered on the app’s page in kanman.
When you ship from Claude Code, an update to an app that lives in a repository opens a merge request there, and Claude passes on its link.
Move an existing app
An app that lives in kanman shows Move this app into a repository on its page once the setting is on. I create the repository from the current version. If I cannot, the page says why: the team has not allowed new repositories, it has no GitLab or GitHub repository to take the group from, or the group set for app repositories is not one of the team’s.
Related
Last updated: January 1, 0001
Open kanman