Connecting GitHub

Kiwami connects to GitHub through a GitHub App installation, not a personal access token — the permissions it has are exactly the repositories you choose to install it on, and they can be revoked at any time from your GitHub account's installed-apps settings.

Installing the app

From your organization's dashboard (or from the New Project wizard, if you haven't connected GitHub yet), click Connect GitHub. You'll be sent to GitHub's own "install this App" page, where you choose which repositories to grant access to — all of them, or a specific list.

GitHub redirects you back to Kiwami once you've finished, and your organization's GitHubConnection is created automatically. You only need to do this once per organization; every project in that organization can pick from the same connection's repositories.

What this enables

• Repository access for cloning during an environment build — Kiwami mints a short-lived installation token per clone, never a long-lived credential.
• Push-triggered rebuilds. A push to a project's configured default branch automatically rebuilds its environment and runs every suite — see Triggering runs.
• Commit statuses. Once a push-triggered run finishes, Kiwami reports the result back to GitHub as a commit status, the same check row a pull request author already expects from any CI system.

What's not covered yet

A push to a feature branch or a pull request branch doesn't trigger anything today — only a push to the project's own default branch does. Per-PR checks are real, planned future work, not something this version does.

Next: Creating a project.