Skip to content

Bump to hlint-3.10 #11082

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Bump to hlint-3.10 #11082

wants to merge 2 commits into from

Conversation

philderbeast
Copy link
Collaborator

Bumps to hlint-3.10 and updates the .hlint.yaml configuration.

Include the following checklist in your PR:

  • 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
Bump counts with hlint-3.8
a6e4162
@philderbeast
Bump to hlint-3.10
e55b866 
- Bump to hlint-3.10 in the gh-action
@ffaf1
Copy link
Collaborator

ffaf1 commented Jul 20, 2025

I see we got fewer occourrences of some warning, I suppose that means hlint got more precise?

@philderbeast
Copy link
Collaborator Author

Label merge+no rebase is necessary when the pull request is from an organisation.

@mergify mergify bot added the ready and waiting Mergify is waiting out the cooldown period label Jul 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@geekosaur geekosaur geekosaur approved these changes

@ulysses4ever ulysses4ever ulysses4ever approved these changes

@ffaf1 ffaf1 ffaf1 approved these changes

Assignees
No one assigned
Labels
merge+no rebase ready and waiting Mergify is waiting out the cooldown period
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@philderbeast @ffaf1 @geekosaur @ulysses4ever