Skip to content

merge queue: embarking master (59804a9) and #11339 together#11600

Closed
mergify[bot] wants to merge 2 commits intomasterfrom
mergify/merge-queue/b5658a3a3d
Closed

merge queue: embarking master (59804a9) and #11339 together#11600
mergify[bot] wants to merge 2 commits intomasterfrom
mergify/merge-queue/b5658a3a3d

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Mar 9, 2026

✨ The merge conditions cannot be satisfied due to failing checks. ✨

Branch master (59804a9) and #11339 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #11339.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

  • any of [🛡 GitHub branch protection]:
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
    • check-success = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Meta checks
    • check-skipped = Meta checks
    • check-success = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
    • check-success = Bootstrap post job
  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • 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 = 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:

---
checking_base_sha: 59804a9f1266846e68242619ab859b02fe9a4d69
previous_failed_batches: []
pull_requests:
  - number: 11339
...

geekosaur and others added 2 commits March 6, 2026 21:28
This may count as "significant" since it's a new command line
option, but it's deliberately out of the way.
@mergify mergify bot mentioned this pull request Mar 9, 2026
6 tasks
@mergify mergify bot closed this Mar 9, 2026
@mergify mergify bot deleted the mergify/merge-queue/b5658a3a3d branch March 9, 2026 23:21
@geekosaur
Copy link
Collaborator

Hackage is having problems again, so I'll let this sit for a while and then kick the PR again.

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.

2 participants