Skip to content

Give the merge queue 120 minutes for checks - #1374

Merged
mergify[bot] merged 1 commit into
mainfrom
stack/EdbertChan/queue-checks-timeout-120/give-merge-queue-120-minutes-checks--23c2694d
Oct 13, 2026
Merged

mergify[bot] merged 1 commit into
mainfrom
stack/EdbertChan/queue-checks-timeout-120/give-merge-queue-120-minutes-checks--23c2694d

Conversation

@EdbertChan

@EdbertChan EdbertChan commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

Summary

The merge queue gives each pull request 60 minutes for its checks to pass. If a check is still running at 60 minutes, the queue rejects the pull request.

The longest check takes about 54 minutes on its own. Several pull requests have been rejected for running out of time.

This raises the limit to 120 minutes.

Review Claim

Approve raising the merge queue's time limit for checks from 60 to 120 minutes.

Review Lane

policy

Review Unit

policy

Safety Invariant

It only gives queued pull requests more time before rejection. The checks that must pass (lint, test, validate) are unchanged. A stuck check can now hold the queue up to an hour longer before it fails.

Slice Rationale

This is one setting in one file, a different claim from the guard change, so it ships alone.

Non-goals

  • No change to which checks are required.
  • No change to batching or to who can queue.
  • No speed-up of the checks themselves.

Measured

Command: gh api repos/EdbertChan/catstack/actions/runs/<id>/jobs, read for the run every tests/ dir step on the latest completed main run

  • base: checks_timeout: 60min and main test step run every tests/ dir duration_min 54.0 success
  • head: checks_timeout: 120min

Test Plan

Test Plan
  • python3 engine/skills/make-pr/scripts/preflight.py --base origin/main --dry-run printed neutral 1 file(s): .mergify.yml and ok preflight passed
  • Not run: parsing the file as YAML locally. Blocker: no YAML library is installed in this environment; Mergify's own configuration check runs on the pull request

Revert Plan

Revert Plan
  • Safe to revert? Yes
  • Revert command: git revert <sha>
  • Post-revert steps: None
  • Data migration? No

🤖 Generated with Claude Code

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Change-Id: I23c2694dffd06040b854425181c3f91db98e3a83
@cursor

cursor Bot commented Oct 13, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: ea0d0551-62eb-4666-823a-f206511413df)

@EdbertChan

Copy link
Copy Markdown
Owner Author

@Mergifyio queue

@mergify

mergify Bot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 2 hours 1 minute 46 seconds in the queue, including 2 hours 55 seconds running CI.

Required conditions to merge
  • check-success = lint
  • check-success = test
  • check-success = validate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant