GitQueue manages your PRs intelligently!

Did you know that on High-stakes Repositories...

Time lost per engineer

On average, each engineer waits about 2 hours every day for PRs to merge

Monthly expense
$0
per month
CI load for 50-dev team

For a 50‑developer team, GitHub Actions consumes 9,277,320 seconds of CI time

Monthly expense
$0
per month
Save these costs now

For High Velocity Teams

Managing PRs in a monorepo is a nightmare

Merge Conflicts

First PR merges, everyone else needs to update their branch

Developer Frustration

Constantly updating branches and re-running tests manually

Wasted CI Time

Teams keep re-running branch updates and merge validation after every base change

The Solution

GitQueue manages your PR merge lanes intelligently

Automated Lane Management

GitQueue manages explicit merge lanes, re-checks fresh GitHub state before merging, updates stale branches automatically, and keeps work moving when a PR is temporarily not merge-ready.

  • Explicit five-lane priority model
  • Three-gate merge decisions
  • Automatic stale-branch recovery
  • Role-based lane access
PR #1
completed
PR #2
active
PR #3
pending
PR #4
pending

Core Features

Everything you need to manage merge lanes at scale

Comment-Based Commands

Control merge lanes directly from PR comments. Use /gitqueue add, remove, status, clear, block, and unblock without leaving GitHub.

Priority Merge Lanes

Five explicit lanes from highest to lowest. Critical fixes jump ahead while lower-priority work keeps its own place and does not rewrite the whole queue.

Three-Gate Processing

GitQueue tracks exactly three gates: Checks, Approval, and Freshness. Freshness warns trigger branch updates, pending gates wait in place, and failures move to lane end.

Role-Based Permissions

Admins control highest and admin commands, CODEOWNERS can use high, and write users can manage normal, low, and lowest lanes.

Persistent Overview Comment

Each PR keeps one top-level GitQueue comment that switches between general and queued modes, includes Activity, and links to the repository queue page.

Web Status Page

Repository-scoped visibility with GitHub OAuth authentication. See queued and processing PRs, gate states, failure reasons, and activity logs in one place.

Simple Command Interface

Manage merge lanes with simple GitHub comments

/gitqueue add

Add PR to the lowest lane by default

/gitqueue add normal

Add PR to the normal ready-work lane

/gitqueue add highest

Add PR to the highest lane (admin only)

/gitqueue remove

Remove PR from its current lane

/gitqueue status

Refresh queued PR status details

/gitqueue block

Block repository lane processing (admin)

GitQueue command interface showing /gitqueue add command

Add PRs to a lane with a simple comment

Priority Merge Lanes

Five priority levels to match your workflow needs

Highest

Repository Admins

Admin-only emergency lane for critical production fixes

High

CODEOWNERS only

High-priority lane reserved for repository CODEOWNERS

Normal

Write Access

Ready-work lane for standard feature development

Low

Write Access

Ready-work lane for lower-priority improvements

Lowest

Write Access

Accepts PRs with pending or warming-up gate states

Three-Gate Processing

Fresh GitHub data decides what merges, waits, or moves to the end

GitQueue overview showing Checks, Approval, and Freshness gate status

Real-time gate status in PR overview

Checks

Derived from GitHub merge state and required check contexts, including pass, warn, pending, and fail outcomes

Approval

Derived from GitHub reviewDecision and passes when GitHub has no blocking review state

Freshness

Uses GitHub REST pull request data plus compare results to detect stale, pending, and failing branch states

Automatic Recovery

When Freshness is warn, GitQueue automatically updates the branch and waits for the next processing cycle. Pending gate states keep the PR in place instead of treating it as a failure.

Web Status Page

Real-time visibility into repository merge lanes

GitQueue status page showing merge lanes with PR positions, Checks, Approval, Freshness, and activity

View queued and processing PRs for a repository on the web status page

Role-Based Permissions

Security and control based on GitHub repository roles

Repository Admin

  • Add/remove PRs in all lanes
  • Access highest priority lane
  • Clear specific or all lanes
  • Block/unblock repository processing

CODEOWNERS

  • Add PRs to high lane
  • Manage normal/low/lowest with write access
  • Remove own PRs from any lane
  • No admin-only controls

Write Access

  • Add/remove PRs in normal lane
  • Add/remove in low/lowest lanes
  • Remove own PRs from any lane

How It Works

Four steps from PR open to safe merge

Read the full guide
01

Open a PR

GitQueue posts one persistent overview comment with Command Help, activity history, and lane eligibility.

02

Add to Lane

Comment to place the PR in a merge lane. /gitqueue add.

03

Process Gates

GitQueue processes lanes by priority. Each PR passes through Checks, Approval, and Freshness from fresh GitHub data before merging.

04

Merge or Requeue

Passing PRs merge automatically. Stale branches stay in lane for retry; irrecoverable failures move to lane end for the next cycle.

Simple pricing

GitHub Marketplace plans with repository entitlements and active PR limits per repository.

Starter

Free trial
$199
per month
  • 1 active repository entitlement
  • 10 active processing PRs in queue per repository
  • Unlimited users
  • 1-month free trial
Start for Free

Scale

Most popular
$499
per month
  • 5 active repository entitlements
  • 50 active processing PRs in queue per repository
  • Unlimited users
  • No free trial
Install

Pro

$999
per month
  • 10 active repository entitlements
  • 100 active processing PRs in queue per repository
  • Unlimited users
  • No free trial
Install

By The Numbers

Real impact on your development workflow

78%
Faster Merges
45%
Less CI Time
100%
Automated
0%
Manual Updates

Ready to Streamline Your PR Workflow?

Join thousands of teams already using GitQueue

Get Started