Skip to content

merge queue: checking master (bc27d17) and [#11787 + #11769] together#12049

Closed
mergify[bot] wants to merge 4 commits into
masterfrom
mergify/merge-queue/5f5e8ad782
Closed

merge queue: checking master (bc27d17) and [#11787 + #11769] together#12049
mergify[bot] wants to merge 4 commits into
masterfrom
mergify/merge-queue/5f5e8ad782

Conversation

@mergify

@mergify mergify Bot commented Jun 28, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

🕵️ This combination of pull requests has failed checks. Mergify will split this batch to understand which pull request is responsible for the failure. 🕵️

Branch master (bc27d17) and [#11787 + #11769] are queued together for merge.

This pull request has been created by Mergify to check the mergeability of [#11787 + #11769].
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]
  • #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: bc27d17d93851f78070be6f8ee0724f58168ee97
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 11787
    scopes: []
  - number: 11769
    scopes: []
scopes: []
...

sheaf and others added 4 commits June 27, 2026 14:43
@sheaf
cabal-install: add --build-timings flag
68a73d0 
This new flag makes cabal-install dump timing information for the
various stages of building a package. This allows us to better see how
much time is spending in configure/build stages.
@sheaf
Add program prefix and suffix to BuildOptions
75389a9 
This commits adds two new fields of `BuildOptions`, namely `programPrefix`
and `programSuffix`. This allows the installed executable program prefix
and suffix to be set by `SetupHooks` for packages with `build-type: Hooks`.

Fixes #11168
@mergify
Merge of #11787
71783fc
@mergify
Merge of #11769
bc27e5d
This was referenced Jun 28, 2026
Merged
Merged
@mergify mergify Bot closed this Jun 28, 2026
@mergify mergify Bot deleted the mergify/merge-queue/5f5e8ad782 branch June 28, 2026 14:29
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

@sheaf