Skip to content

merge queue: checking #814 on main (78415d7), stacked on #808 - #820

Closed
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/0975d743b8
Closed

mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/0975d743b8

Conversation

@mergify

@mergify mergify Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

#814 is queued for merge on branch main (78415d7).

Stacked behind 1 pull request queued ahead of this batch, not part of it. These checks run on a tip that also carries its commits, so a failure here can come from it as much as from #814.

Queued ahead of this batch:

This pull request has been created by Mergify to speculatively check the mergeability of #814.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

  • check-success = gates (linux)
  • check-success = gates (windows)
  • check-success = red-first
  • github-review-approved [🛡 GitHub repository ruleset rule main-pr-required-checks]
  • label != do-not-merge
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (linux)
    • check-neutral = @github-actions/gates (linux)
    • check-skipped = @github-actions/gates (linux)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (windows)
    • check-neutral = @github-actions/gates (windows)
    • check-skipped = @github-actions/gates (windows)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/red-first
    • check-neutral = @github-actions/red-first
    • check-skipped = @github-actions/red-first
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections

Required conditions to stay in the queue:

---
all_scopes: false
checking_base_sha: 5caf509eb75f3e48fa8b7af556720b4aaacf315f
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 814
    scopes: []
scopes: []
...

Cuarroc and others added 4 commits October 9, 2026 04:18
No-Test: coverage-only tests for existing controls (DR-SEC-01c)
Concurrent run-local.sh runs in one checkout overwrote FETCH_HEAD, so each
prompt could review the wrong PR. Fetch into refs/pa-review/pr-<n> and record
Head: in the prompt.

Test-First: scripts/test-review-local.sh::parallel PR fetches keep distinct diffs (no shared FETCH_HEAD)
Co-authored-by: Cursor <cursoragent@cursor.com>
@mergify mergify Bot closed this Oct 9, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/0975d743b8 branch October 9, 2026 03:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant