Merge & Pull Requests
Merge & Pull Requests lists open GitHub pull requests, GitLab merge requests, and Bitbucket pull requests in one place, each linked to the initiative, bug, synced issue, or todo it completes.
Review open pull requests
Open an item to see its branch, description, review status, and linked work. When an agent opened or worked on the pull request, the detail view also shows the agent sessions and their activity.
Once merged, pull requests count as completed work, so recaps and insights show what shipped.
Provider coverage
| Provider | What appears here |
|---|---|
| GitHub | Pull requests, review state, branches, descriptions, and linked work. |
| GitLab | Merge requests from connected GitLab.com projects. GitLab is currently in private beta. |
| Bitbucket | Pull requests from connected Bitbucket Cloud workspaces. Bitbucket is in private beta. |
Link pull requests to work
Put the One Horizon task ID in the pull request title or branch name to link it to the initiative, bug, or todo it implements. Review, completion, recaps, and roadmap progress then all point at the same item. In spec-driven development, this is how the result links back to the spec.
GitHub pull request summaries
The GitHub App writes a structured summary on each pull request and updates it as commits land. When the title includes task IDs, the summary links the matching initiatives, bugs, or todos.
Automate pull requests
Agents and scripts can list, open, and update pull requests through the MCP server or the REST API. Calls use the signed-in member's repository access. The head branch must already be pushed before you open a pull request.
Review activity from all three providers feeds Pull Request Flow, which tracks volume, lead time, cycle time, review lag, and merge rate.