Skip to content

Follow hlint suggestion: evaluate#11627

Open
philderbeast wants to merge 2 commits intohaskell:masterfrom
cabalism:hlint/evaluate
Open

Follow hlint suggestion: evaluate#11627
philderbeast wants to merge 2 commits intohaskell:masterfrom
cabalism:hlint/evaluate

Conversation

@philderbeast
Copy link
Collaborator

See #9110. Discharges and no longer ignores HLint's "evaluate" suggestion so that this will be suggested by our CI linting.

I'll squash commits before applying the merge label if this pull request is approved.


  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

@philderbeast philderbeast added the merge me Tell Mergify Bot to merge label Mar 19, 2026
@mergify mergify bot added ready and waiting Mergify is waiting out the cooldown period merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days queued labels Mar 19, 2026
@mergify
Copy link
Contributor

mergify bot commented Mar 21, 2026

Merge Queue Status

This pull request spent 14 minutes 3 seconds in the queue, including 3 minutes 10 seconds running CI.

Required conditions to 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

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

mergify bot added a commit that referenced this pull request Mar 21, 2026
@philderbeast philderbeast force-pushed the hlint/evaluate branch 2 times, most recently from 52053af to b8af3eb Compare March 21, 2026 18:09
- Remove redundant brackets
- Rerun hlint --default for counts
- Add --ignore-glob for ghc-supported-languages
@philderbeast
Copy link
Collaborator Author

@mergify enqueue

@mergify
Copy link
Contributor

mergify bot commented Mar 21, 2026

enqueue

❌ Sorry but I didn't understand the command. Please consult the commands documentation 📚.

@philderbeast
Copy link
Collaborator Author

@mergify refresh

@mergify
Copy link
Contributor

mergify bot commented Mar 21, 2026

refresh

✅ Pull request refreshed

@philderbeast
Copy link
Collaborator Author

@mergify queue

@mergify
Copy link
Contributor

mergify bot commented Mar 21, 2026

Merge Queue Status

  • 🟠 Waiting for queue conditions
  • ⏳ Enter queue
  • ⏳ Run checks
  • ⏳ Merge
Required conditions to enter a queue
  • any of [🔀 queue conditions]:
    • all of [📌 queue conditions of queue default]:
      • 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
    • all of [📌 queue conditions of queue squash-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
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of [📌 queue -> configuration change requirements]:
    • -mergify-configuration-changed
    • check-success = Configuration changed

@geekosaur
Copy link
Collaborator

@Mergifyio rebase

@mergify
Copy link
Contributor

mergify bot commented Mar 22, 2026

rebase

❌ Pull request can't be updated with latest base branch changes

Details

Mergify needs the author permission to update the base branch of the pull request.
@philderbeast needs to authorize modification on its head branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge ready and waiting Mergify is waiting out the cooldown period

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants