GitHub
Connect GitHub to bring commits, pull requests, issues, and review activity into recaps, planning, delivery, and insights.
GitHub has two connection paths:
| Connection | Use it for |
|---|---|
| Personal GitHub connection | Attribute commits, pull requests, issues, and reviews to the right developer. |
| GitHub PR Bot | Add structured pull request summaries and feed pull request analytics. |
Personal GitHub connection
Each developer connects their personal GitHub account so commits and pull requests can be attributed correctly. GitHub OAuth is used, and GitHub remains the place that controls repository access.
To connect, open GitHub integration settings, select the organizations to include, and authorize access in GitHub. After that, commits, pull requests, and issues from connected organizations can appear in Recaps, Planning, Pull Requests, and Insights.
By default, we focus on organizations you connect. Personal repositories are off by default and can be enabled from GitHub integration settings. You can exclude whole organizations or individual repositories when their activity should not feed recaps or insights.
When an organization is connected, any team member with access to that organization can connect their own GitHub account and get summaries for repositories they can access.
Commit summaries and attribution
Commits from connected repositories can be analyzed and grouped into daily work summaries. Those summaries help explain what changed without asking developers to write the same update again.
If commit comments are enabled, a summary can also be posted back to the commit. Disable commit comments if your team prefers to keep GitHub commit pages clean.
When a commit message includes a recognized Co-Authored-By trailer from an AI coding tool, the resulting work can include agent attribution with the tool name and provider. That attribution shows where tools such as Claude, GitHub Copilot, Codex, Cursor, or other coding agents contributed without changing how developers commit.
Settings
| Setting | What it controls |
|---|---|
| Include personal repositories | Includes commits and pull requests from personal repositories. Organization repositories stay the default. |
| Enable contributions | Includes activity from repositories you contribute to, even when the repository is not owned by an organization you belong to. |
| Exclude organizations | Stops activity from selected organizations from feeding recaps, planning, and insights. |
| Exclude repositories | Stops selected personal, contribution, or organization repositories from being tracked. |
| Disable commit comments | Prevents commit summaries from being posted back to GitHub. |
GitHub PR bot
Install the GitHub PR Bot at the workspace level to keep pull requests readable and enable PR analytics. The bot can add a structured summary to the pull request body, update it on each push, and post concise comments as the PR evolves.
The bot is installed as a GitHub App, and repository access is controlled in GitHub through organization and repository selection.
The PR Bot is installed at the workspace level. Each developer should still connect their personal GitHub account so authorship, review requests, and recap attribution stay accurate.
To install it, open GitHub PR Bot settings and select Install. GitHub will ask which organization and repositories the app can access. To remove it, use the uninstall flow in GitHub or from the workspace integration settings.
The PR summary usually includes a short overview, detailed bullets grouped by area or component, related tickets when detected, an impact checklist, and review focus notes.
When new commits are pushed, the bot can update the top summary and add a concise comment so reviewers can see what changed since the last pass.
You can exclude repositories from PR Bot summaries when a repository should not receive automated PR body updates or comments.
Where GitHub activity appears
GitHub activity can become completed work, review work, and delivery metrics when it is linked to the work it moved forward.
Pull requests you opened, are assigned to, or need to review can appear in planned work. Merged pull requests can move into completed work. The capture model is covered in Captured Work.
GitHub Issues can appear as synced issues when they are captured from connected repositories. Bugs are for defects or incidents; keep issue planning in GitHub when it remains the system of record.
After GitHub is connected, Merge & Pull Requests shows review work and Pull Request Flow tracks review and merge pace.
Security and access
We never ask for your GitHub password. Personal GitHub connections use OAuth, and the PR Bot uses a GitHub App installation.
GitHub controls which organizations and repositories are available. We only use data from repositories you grant access to, and we do not store your source code.
To revoke access, remove the OAuth connection or GitHub App installation from GitHub.