GitHub
Connect GitHub to work with remote repos, run agent workflows, and bring commits, pull requests, issues, and reviews into recaps, planning, delivery, and insights.
GitHub has two connections. Most teams set up both: each developer connects a personal account, and an admin installs the GitHub App once for the workspace.
1. Connect your personal GitHub account
The personal connection attributes commits, pull requests, issues, and reviews to the right developer, and lets agent workflows read the repos that account can access. It uses GitHub OAuth.
Open GitHub integration settings, select the organizations to include, and authorize access in GitHub. Activity from connected organizations can then appear in Recaps, Planning, Pull Requests, and Insights.
Once an organization is connected, any team member with access to it can connect their own GitHub account and get summaries for the repositories they can access.
2. Install the GitHub App
The GitHub App lets agents and workflows push commits and open pull requests. It can also add structured summaries to pull requests and feed pull request analytics.
Open GitHub App settings and select Install. GitHub asks which organization and repositories the app can access. To remove it, use the uninstall flow in GitHub or the workspace integration settings.
The app is installed at the workspace level. Each developer still needs a personal GitHub connection so authorship, review requests, workflow attribution, and recap attribution stay accurate.
Pull request summaries
The app can add a summary to the pull request body. It usually includes a short overview, bullets grouped by area or component, related tickets when detected, an impact checklist, and review focus notes. When new commits are pushed, the app can update the summary and add a short comment on what changed since the last review.
When the pull request title includes One Horizon task IDs, the summary adds a Linked tasks section right after the overview. Each line shows the work type (Bug, Initiative, or TODO) and links to the task in the dashboard. Put the ID in the title, for example Fix auth redirect (tskAbc123) or tskAbc123 Fix auth redirect. Copy the ID from the task URL or the task's copy-link action.
Exclude a repository from GitHub App automation when it should not receive workflow commits, PR body updates, or PR comments.
Where GitHub activity appears
Pull requests you opened, are assigned to, or need to review can appear in planned work, and merged pull requests can move into completed work. Captured Work covers the capture model. Merge & Pull Requests shows review work, and Pull Request Flow tracks review and merge pace.
GitHub Issues from connected repositories can appear as synced issues. Keep issue planning in GitHub when it remains the system of record; Bugs are for defects and incidents.
Commit summaries and attribution
Commits from connected repositories can be grouped into daily work summaries. If commit comments are enabled, the summary can also be posted to the commit.
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
Change these settings in GitHub integration 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. |
Need an admin to approve it?
If your organization requires approval before GitHub can be connected, send your admin this request. It explains what the connection is for and which permissions it asks for.
Security and access
We never ask for your GitHub password. GitHub controls which organizations and repositories are available, through your OAuth grant and the repositories selected when the app is installed. 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.