Getting startedSet up integrationsCreate your first initiativeInvite your teamPlan today's workShare your first update
Spec-driven developmentAI HandoffMerge & Pull RequestsCommentsSlack 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 or GitLab merge 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 and GitLab merge 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 and GitLab merge 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.
BitbucketPlanned support for Bitbucket pull requests. Until the connector is enabled, Bitbucket activity does not appear here.

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.

GitHub PR bot

The GitHub PR Bot can write and update a structured summary on GitHub pull requests as commits change. Setup and behavior live on the GitHub integration page.

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

PreviousAI HandoffNextComments

AI Handoff

Send work into coding tools, terminal workflows, or agents with controlled orchestration.

Comments

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

Slack Discussions

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

Initiatives & Bugs

Use initiatives for planned work and bugs for defects or incidents before work moves into planning or delivery.

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