Skip to content

merge queue: checking #12549 on master (22b6bf9) - #12577

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

mergify[bot] wants to merge 3 commits into
masterfrom
mergify/merge-queue/1bc8d0d892

Conversation

@mergify

@mergify mergify Bot commented Nov 11, 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 plausible-clafoutis-q6ut8p of the default queue, to test #12549 before it merges into master. Pushing to this branch or closing this pull request removes #12549 from the queue.

What this draft tests

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

  1. master at 22b6bf9
  2. #12549, the pull request of this batch

⏳ Where it stands: being checked

CI is running on this draft.

Waiting for any of

  • check-neutral = Validate post job
  • check-skipped = Validate post job
  • check-success = Validate post job

Follow the default queue in the dashboard

What happens next

  • Once the checks pass and every merge condition is met, Mergify merges #12549 into master and closes this draft.
  • If a check fails, Mergify removes #12549 from the queue and closes this draft.
Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: 22b6bf910d5b98bfef3e24d29e355578ef013332
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 12549
    scopes: []
scopes: []
...
Required conditions of queue rule default for merge
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • github-review-approved [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = hlint
    • check-neutral = hlint
    • check-skipped = hlint
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs
Required conditions to stay in the queue

swinilohani616-dot and others added 3 commits November 8, 2026 02:06
The legacy note shown by `cabal v1-*` commands linked to
nix-local-build-overview.html, which now 404s on the user guide.
Point it at nix-local-build.html instead, and update the generated
help text in doc/cmd-v1-help to match.
@mergify mergify Bot mentioned this pull request Nov 11, 2026
5 of 6 tasks
@mergify mergify Bot closed this Nov 11, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/1bc8d0d892 branch November 11, 2026 21:17
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