Skip to content

merge queue: checking #12250 on master (27e758b) - #12483

Closed
mergify[bot] wants to merge 2 commits into
masterfrom
mergify/merge-queue/b8997dc1e4
Closed

merge queue: checking #12250 on master (27e758b)#12483
mergify[bot] wants to merge 2 commits into
masterfrom
mergify/merge-queue/b8997dc1e4

Conversation

@mergify

@mergify mergify Bot commented Oct 24, 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 sharing-baba-xoi6w8 of the default queue, to test #12250 before it merges into master. Pushing to this branch or closing this pull request removes #12250 from the queue.

What this draft tests

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

  1. master at 27e758b
  2. #12250, 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 #12250 into master and closes this draft.
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: 27e758be0b1a450e37dcc551d553a388fa1497dc
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 12250
    scopes: []
scopes: []
...
Required conditions of queue rule default for merge
  • #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 = Validate post job
    • check-neutral = Validate post job
    • check-skipped = Validate post job
  • 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

@mergify mergify Bot mentioned this pull request Oct 24, 2026
Merged
2 tasks done
@mergify mergify Bot closed this Oct 24, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/b8997dc1e4 branch October 24, 2026 10:58
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

@Mikolaj