Skip to content

merge queue: checking #793 on main (a350d64), stacked on #782 - #798

Closed
mergify[bot] wants to merge 5 commits into
mainfrom
mergify/merge-queue/14090a937a
Closed

mergify[bot] wants to merge 5 commits into
mainfrom
mergify/merge-queue/14090a937a

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. 🎉

#793 is queued for merge on branch main (a350d64).

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 #793.

Queued ahead of this batch:

This pull request has been created by Mergify to speculatively check the mergeability of #793.
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
  • all of [🛡 Merge Protections rule Paket-PR bringt seinen Bericht mit]:
  • 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: 4c936a06f10e875f28b75006541997f7e7220a38
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 793
    scopes: []
scopes: []
...

Cuarroc and others added 5 commits October 9, 2026 02:13
Test-First: scripts/lib/dev-mrp-count.test.mjs::countRp recognizes all current Mergify package branches
Test-First: scripts/lib/dev-bench-weekly.test.mjs::weekly package counts follow current Mergify prefixes and preserve package IDs
Test-First: scripts/lib/dev-mrp-count.test.mjs::countRp recognizes all current Mergify package branches
Test-First: scripts/lib/dev-bench-weekly.test.mjs::weekly package counts follow current Mergify prefixes and preserve package IDs
No-Test: coverage-only tests for existing controls (DR-SEC-01b)
@mergify mergify Bot closed this Oct 9, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/14090a937a branch October 9, 2026 01:38
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