Repository activity with project context
Review commits, pull requests, branches, files, and issues beside project ownership, status, tasks, and meetings rather than relying on isolated links in chat.
What you can do
Connect GitHub with Kato’s GitHub App to see commits, pull requests, branches, files, issues, and more on your Project records. Link a repository once, then stay up to date without leaving Kato.
Focused repository access
The GitHub App installation lets an account or organization choose which repositories Kato can reach instead of requiring blanket access to every codebase.
Fresher delivery signals
Incoming GitHub events keep relevant project activity current, helping account and delivery teams recognize movement without asking engineers for another manual update.
Inside Kato
Connect GitHub
Click Connect to install the Kato GitHub App and authorize your account. Choose which repositories Kato can access. On any Project, open the GitHub tab to link a repo — Overview, Commits, PRs, Issues, and other sections load from GitHub using your connection. Incoming webhooks keep activity fresh when pushes or PR events occur.
- 01Open Settings → Integrations → GitHub and click Connect.
- 02Install the Kato GitHub App on your personal account or organization and select the repositories Kato should access.
- 03Authorize Kato when GitHub prompts you — credentials are handled by the app (you never paste a Client ID or Secret).
- 04On a Project record, open the GitHub tab and link a repository. If Issues or Actions are empty, open Connections → Configure on the GitHub App install and grant those permissions, then refresh.
Made for your workflow
Release preparation
Review open pull requests and recent commits from the project record before a release meeting, then turn unresolved work into explicit Kato tasks.
Client status updates
Give account owners enough repository context to prepare an accurate progress summary while deeper code review stays in GitHub.
Issue-to-work coordination
Use linked GitHub issues as technical evidence while Kato remains the place for assignment, schedules, meeting follow-ups, and cross-functional planning.
Common questions
How does GitHub connect to Kato?
Kato uses a GitHub App installation and authorization flow. The installer selects the repositories the app can access, and teammates then link an available repository to a Kato project.
Does Kato replace GitHub issues or pull requests?
No. GitHub remains the source for code, reviews, branches, and issues. Kato presents that activity in project context and coordinates the broader work around it.
Can access be limited to selected repositories?
Yes. GitHub App installation settings support selecting repositories. Teams should grant only the repositories that need to appear in the connected Kato workspace.
Last updated Jul 18, 2026