-
-
Notifications
You must be signed in to change notification settings - Fork 22
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.
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
Add HLint #70
Add HLint #70
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution, @blackheaven!
I have a few questions and suggestions to clarify the proper CI configuration though
.github/workflows/hlint.yml
Outdated
- name: 'Set up HLint' | ||
uses: rwe/actions-hlint-setup@v1 | ||
with: | ||
version: '3.1.6' | ||
|
||
- name: 'Run HLint' | ||
uses: rwe/actions-hlint-run@v2 | ||
with: | ||
path: '["src/", "test/"]' | ||
fail-on: warning |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't used rwe/actions-hlint-setup
and rwe/actions-hlint-run
actions before.
I would prefer to use official Haskell actions under the haskell
github org:
But even then, I'm not sure what is the difference between those two actions and a simple job that just downloads the hlint
executable and runs it. I used to configure hlint
before with this simple setup:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIUC:
rwe/actions-hlint-setup
deals with the subtleties of the underlying OS (ie. download leexe
on windows, and on)rwe/actions-hlint-run
only run hlint on the new/changed files
I update the PR according to your feedback, I'm open to new comments/requests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@blackheaven Thanks a lot for the contribution! I agree that we can always improve the action further if we find lacking something but for now we can start with the simplest thing that works 🙂
I'm trying to tackle #63