Skip to content

merge queue: embarking master (baa8448) and #11771 together#11800

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

merge queue: embarking master (baa8448) and #11771 together#11800
mergify[bot] wants to merge 2 commits into
masterfrom
mergify/merge-queue/d99da0737d

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented May 8, 2026

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

Branch master (baa8448) and #11771 are embarked together for merge.

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

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
  • #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 = 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:

---
checking_base_sha: baa8448b9728d947817171c9f3343956c85280b6
previous_failed_batches: []
pull_requests:
  - number: 11771
    scopes: []
scopes: []
...

sheaf and others added 2 commits May 6, 2026 10:12
Adds a how-to guide in the Cabal's user guide.

Changes to the SetupHooks module and Haddocks:

  - Add an usage overview that explains what the various hooks may
    be useful for.
  - Add a worked example for 'dynamicRule' as it is the most complex
    aspect of the API.
  - Unexpose the gnarly 'RuleCommands' constructors, advising usage of
    'staticRule' and 'dynamicRule' instead.
  - Various small tweaks, including additional haddock comments for
    'dynamicRule'.

Fixes #11461
@mergify mergify Bot closed this May 8, 2026
@mergify mergify Bot deleted the mergify/merge-queue/d99da0737d branch May 8, 2026 11:47
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