Skip to content

merge queue: checking #279 on main (f33f40d) - #280

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/2b8bb24c4d
Closed

mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/2b8bb24c4d

Conversation

@mergify

@mergify mergify Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

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

#279 is queued for merge on branch main (f33f40d).

This pull request has been created by Mergify to check the mergeability of #279.
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:

Required conditions to stay in the queue:

---
checking_base_sha: f33f40d5fd6e191cdf04b113d170e26499422190
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 279
    scopes: []
scopes: []
...

Cuarroc and others added 2 commits October 4, 2026 11:22
AGENTS.md and docs/setup/mergify.md said every eligible PR is queued
automatically. Observed on 2026-10-04: the last 14 merged PRs (#240-#266)
and the open #274/#275 each carry an explicit "@Mergifyio queue" comment,
so the documented automatic pickup is not what happens in practice.

Keep the eligibility conditions, add the explicit step (gh pr checks <n>,
then comment "@Mergifyio queue") and mark the cause as unresolved. No
change to .mergify.yml, labels, account settings or any PR.

No-Test: documentation-only correction; no runtime effect.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@mergify mergify Bot closed this Oct 4, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/2b8bb24c4d branch October 4, 2026 10:03
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