Skip to content
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

Log which config file was used #610

Closed
2 of 3 tasks
rittneje opened this issue Apr 20, 2021 · 6 comments · Fixed by #615
Closed
2 of 3 tasks

Log which config file was used #610

rittneje opened this issue Apr 20, 2021 · 6 comments · Fixed by #615

Comments

@rittneje
Copy link

  • This is a bug report
  • This is a feature request
  • I searched existing issues before opening this one

It would be helpful if hadolint output a log message indicating which config file it was using. Right now it doesn't say anything, so you can't easily tell. For example, if you accidentally name the file hadolint.yaml instead of .hadolint.yaml, you won't know unless you explicitly test a negative case.

@lorenzo
Copy link
Member

lorenzo commented Apr 21, 2021

Sounds like a good idea, would you like to contribute this feature? @rittneje

@rittneje
Copy link
Author

Unfortunately, my experience with Haskell is rather limited.

@seaerchin
Copy link
Contributor

hi @lorenzo, i'm currently learning haskell and this seems like a good first issue for me to contribute to. would it be possible for me to pick up this issue?

@lorenzo
Copy link
Member

lorenzo commented Apr 23, 2021

@seaerchin sure thing, thanks for stepping up!

Let me know if you need any guidance.

@seaerchin
Copy link
Contributor

will do! reading through the codebase now and should i just post here if i have questions or should i use another medium?

@seaerchin
Copy link
Contributor

i've the PR out here; still new to haskell (and even newer to the codebase) so lmk if there are stuff that should be done differently

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

Successfully merging a pull request may close this issue.

3 participants