Skip to content

merge queue: checking #12396 on master (59f7356) - #12458

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

merge queue: checking #12396 on master (59f7356)#12458
mergify[bot] wants to merge 2 commits into
masterfrom
mergify/merge-queue/b12b520dc2

Conversation

@mergify

@mergify mergify Bot commented Oct 14, 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 dry-roquefort-wbipui of the default queue, to test #12396 before it merges into master. Pushing to this branch or closing this pull request removes #12396 from the queue.

What this draft tests

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

  1. master at 59f7356
  2. #12396, 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 #12396 into master and closes this draft.
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: 59f735663d248b552724d087c3113051c255c32e
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 12396
    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

philderbeast and others added 2 commits October 12, 2026 08:52
@philderbeast
Remove GHCJS module and tests
0c4b18a 
- Remove the --ghcjs flag
- Remove the ghcjs and ghcjs-pkg builtin programs
- Use uhc instead in tests that used ghcjs
- Give a dedicated error when GHCJS is selected
- ghcjs-* in a pkg ignored, in a project warned
@mergify @mergify-commit-signer
Merge of #12396
c8cc0f0
@mergify mergify Bot mentioned this pull request Oct 14, 2026
Merged
6 tasks done
@mergify mergify Bot closed this Oct 14, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/b12b520dc2 branch October 14, 2026 16:57
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

@philderbeast