Getting startedSet up integrationsCreate your first initiativeInvite your teamPlan today's workShare your first update
Spec-driven developmentAI HandoffMerge & Pull RequestsCommentsWork InboxSlack Discussions
DocsAPI Reference

Main

  • Home
  • About
  • Pricing
  • Vault
  • Changelog
  • Docs

Features

  • Roadmaps
  • Planning
  • Standups
  • Status updates
  • Insights
  • AI assistant / MCP
  • Integrations

Solutions

  • Startups
  • Dev shops / agencies
  • Software teams
  • Internal IT & platform teams

Alternatives

  • vs Jira
  • vs Linear
  • vs Asana
  • vs Monday.com
  • vs ClickUp
  • vs Notion

Company

  • Blog
  • Security
  • Log in
  • Sign up
  • Terms of Use
  • Privacy Policy

Resources

  • Docs
  • Community
  • API reference
  • CLI
  • Desktop app
  • SDK

© 2026 One Horizon. All rights reserved

FacebookInstagramThreadsXRedditTikTokYouTubeMedium

Merge & Pull Requests

Merge & Pull Requests shows code review work from connected version control tools and keeps GitHub pull requests, GitLab merge requests, or Bitbucket pull requests tied to the initiative, bug, synced issue, or todo they complete.

What appears

The view lists open review work from connected version control tools. GitHub pull requests, GitLab merge requests, and Bitbucket pull requests appear together, with branch, description, review status, and linked work available from the detail view.

Open items show what needs review. Merged GitHub pull requests, GitLab merge requests, and Bitbucket pull requests can appear in completed work, so recaps and insights reflect what shipped.

When agent work is tied to a pull request or merge request, the detail view shows the related agent sessions and activity.

Code Review
Reviewed PR #45 for error handling improvements

Provider coverage

ProviderWhat appears here
GitHubPull requests, review state, branches, descriptions, and linked work.
GitLabMerge requests from connected GitLab.com projects. GitLab is currently in private beta.
BitbucketPull requests from connected Bitbucket Cloud workspaces. Bitbucket is in private beta.

Link code to work

In spec-driven development, code review should point back to the initiative, bug, synced issue, or todo it came from. That keeps review, completion, recaps, and roadmap progress tied to the same work.

Automation

Agents and backend jobs can list, open, and update pull requests on connected GitHub, GitLab, and Bitbucket through the MCP server or REST API. The remote head branch must exist before creation. Calls act with the same repository access as the signed-in member.

GitHub PR bot

The GitHub PR Bot can write and update a structured summary on GitHub pull requests as commits change. When the title includes One Horizon task IDs, the summary links to the matching bugs, initiatives, or todos. Setup and behavior live on the GitHub integration page.

GitHub, GitLab, and Bitbucket review activity can feed Pull Request Flow, where teams track volume, lead time, cycle time, review lag, and merge rate.

PreviousAI HandoffNextComments

Comments

Keep discussion around an initiative, bug, or todo attached to the work people inspect later.

AI Handoff

Start an agent workflow, local agent run, or coding-tool handoff from a scoped work item.

Slack Discussions

Slack discussions let teams move a work conversation into the channel where people already collaborate.

REST API

Create, read, and update workspace work from services, scripts, and CI.

  • What appears
  • Provider coverage
  • Link code to work
  • Automation
  • GitHub PR bot
  • Back to top