Skip to content

merge queue: checking #1329 on develop (0130f8e) - #1333

Closed
mergify[bot] wants to merge 31 commits into
developfrom
mergify/merge-queue/7657d6dff6
Closed

mergify[bot] wants to merge 31 commits into
developfrom
mergify/merge-queue/7657d6dff6

Conversation

@mergify

@mergify mergify Bot commented Oct 16, 2026 •

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 resolving-souffle-iwe0d1 of the integration queue, to test #1329 before it merges into develop. Pushing to this branch or closing this pull request removes #1329 from the queue.

What this draft tests

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

  1. develop at 0130f8e
  2. #1329, the pull request of this batch

Impacts all scopes — this batch runs alone and serializes the queue.

🎉 Where it stands: checks passed

CI passed on this draft.

Follow the integration queue in the dashboard

What happens next

  • Mergify merges #1329 into develop and closes this draft.
Metadata for CI tooling, read by mergify ci
---
all_scopes: true
checking_base_sha: 0130f8e713fb2d2f2b7c70ed06b724d9bce36217
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1329
    scopes:
      - core
scopes:
  - core
...
Required conditions of queue rule integration for merge
  • check-success = Conventional Commit title
  • check-success = Queue validation
  • any of [🛡 GitHub repository ruleset rule develop]:
    • check-success = @github-actions/Lint & Format
    • check-neutral = @github-actions/Lint & Format
    • check-skipped = @github-actions/Lint & Format
  • any of [🛡 GitHub repository ruleset rule develop]:
    • 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 develop]:
    • 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 develop]:
    • 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 develop]:
    • 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 develop]:
    • 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 develop]:
    • 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

renovate Bot and others added 30 commits October 15, 2026 15:44
@mergify mergify Bot mentioned this pull request Oct 16, 2026
@mergify mergify Bot closed this Oct 16, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/7657d6dff6 branch October 16, 2026 08:23
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