Skip to content

merge queue: checking #1724 on main (962c78a) - #1725

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

merge queue: checking #1724 on main (962c78a)#1725
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/3487eb8722

Conversation

@mergify

@mergify mergify Bot commented Oct 19, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch glamorous-chataigne-uoekhj of the default queue, to test #1724 before it merges into main. Pushing to this branch or closing this pull request removes #1724 from the queue.

What this draft tests

Mergify checks that #1724 still passes CI on top of main. CI runs on this draft's code, built in this order:

  1. main at 962c78a
  2. #1724, the pull request of this batch

🎉 Where it stands: checks passed

CI passed on this draft.

Follow the default queue in the dashboard

What happens next

  • Mergify merges #1724 into main and closes this draft.
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: 962c78ab71ff64424a554227119b3206507b31bf
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1724
    scopes: []
scopes: []
...
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

Cuarroc and others added 2 commits October 19, 2026 01:29
@Cuarroc @claude
docs(stand): move status lines to origin/main 962c78a
038fc77 
Snapshot line in STAND.md and the status line of the v2.0 plan now
name the current origin/main; the latest release tag v1.6.6 is
unchanged.

No-Test: docs status sync only

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@mergify @mergify-commit-signer
Merge of #1724
e1b26a5
@mergify mergify Bot closed this Oct 19, 2026
@mergify mergify Bot mentioned this pull request Oct 19, 2026
Merged
@mergify
mergify Bot deleted the mergify/merge-queue/3487eb8722 branch October 19, 2026 00:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Cuarroc