Skip to content

merge queue: checking #12310 + #12497 together on master (3c15ba7) - #12575

Closed
mergify[bot] wants to merge 6 commits into
masterfrom
mergify/merge-queue/fdba842f49
Closed

mergify[bot] wants to merge 6 commits into
masterfrom
mergify/merge-queue/fdba842f49

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 structural-painbeurre-lb4sc2 of the default queue, to test #12310 and #12497 before they merge into master.

What this draft tests

Mergify checks that #12310 and #12497 still pass CI on top of master. CI runs on this draft's code, built in this order:

  1. master at 3c15ba7
  2. #12310 + #12497, the pull requests of this batch, tested together as one tip

🕵️ Where it stands: failed, splitting the batch

The checks of this draft failed. Mergify splits this batch to find which pull request is responsible.

Follow the default queue in the dashboard

What happens next

  • Mergify checks smaller batches of #12310 and #12497 until it finds which pull request is responsible.
Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: 3c15ba73db6d66832ababa9ee8082150c3a3cebe
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 12310
    scopes: []
  - number: 12497
    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

sheaf and others added 6 commits November 9, 2026 09:23
Header files named in `includes` and `install-includes` are now looked
up in the same set of directories everywhere, via the new
`Distribution.Simple.BuildPaths.includeSearchDirs`.

This fixes the following issues:

  - A header at the package root (without any `include-dirs`) would not
    be found when compiling C sources.

  - Generated header files for sub-libraries and foreign libraries would
    not be found (we looked under the component's build directory rather
    than the package's).

  - Absolute `include-dirs` entries were silently ignored when locating
    `install-includes` files (#11186).

Fixes #11186

Co-Authored-By: Ilya Baryshnikov <zlonast3@gmail.com>
Co-Authored-By: Plume <leana.jiang+git@icloud.com>
@mergify mergify Bot closed this Nov 11, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/fdba842f49 branch November 11, 2026 19:00
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