Skip to content

merge queue: checking #1302 on master (b48dbb1) - #1325

Closed
mergify[bot] wants to merge 3 commits into
masterfrom
mergify/merge-queue/a0ae6f5085
Closed

merge queue: checking #1302 on master (b48dbb1)#1325
mergify[bot] wants to merge 3 commits into
masterfrom
mergify/merge-queue/a0ae6f5085

Conversation

@mergify

@mergify mergify Bot commented Oct 15, 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 romantic-hure-pjow9j of the default queue, to test #1302 before it merges into master. Pushing to this branch or closing this pull request removes #1302 from the queue.

What this draft tests

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

  1. master at b48dbb1
  2. #1302, 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 #1302 into master and closes this draft.
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: b48dbb1dca7cfbf1cd9de6d5520e68a94012b29d
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1302
    scopes: []
scopes: []
...
Required conditions of queue rule default for merge
  • check-success = Conventional Commit title
  • check-success = Queue validation
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-success = @github-actions/Lint & Format
    • check-neutral = @github-actions/Lint & Format
    • check-skipped = @github-actions/Lint & Format
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-success = @github-actions/NAPI Build (Linux ARM64 GNU)
    • check-neutral = @github-actions/NAPI Build (Linux ARM64 GNU)
    • check-skipped = @github-actions/NAPI Build (Linux ARM64 GNU)
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-success = @github-actions/NAPI Build (Windows)
    • check-neutral = @github-actions/NAPI Build (Windows)
    • check-skipped = @github-actions/NAPI Build (Windows)
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-success = @github-actions/Rust Test & NAPI Build
    • check-neutral = @github-actions/Rust Test & NAPI Build
    • check-skipped = @github-actions/Rust Test & NAPI Build
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-success = @github-actions/JS Test (Ubuntu)
    • check-neutral = @github-actions/JS Test (Ubuntu)
    • check-skipped = @github-actions/JS Test (Ubuntu)
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-success = @github-actions/JS Test (Windows)
    • check-neutral = @github-actions/JS Test (Windows)
    • check-skipped = @github-actions/JS Test (Windows)
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-success = @github-actions/Conventional Commit title
    • check-neutral = @github-actions/Conventional Commit title
    • check-skipped = @github-actions/Conventional Commit title
Required conditions to stay in the queue

@mergify mergify Bot mentioned this pull request Oct 15, 2026
Merged
1 task
@mergify mergify Bot closed this Oct 15, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/a0ae6f5085 branch October 15, 2026 23:59
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

@tignear