-
Notifications
You must be signed in to change notification settings - Fork 16
Feature/fixup pylint example errors #6
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
Feature/fixup pylint example errors #6
Conversation
For now, both calls to Ultimately, at the very least, the checks for library files, |
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.
Checked the actions output. pylint ran as part of pre-commit and not its own action.
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.
Thank you so much for doing this! Let's hold off on this PR though, and get it into cookiecutter
first if this is how it should be done. We'll do a patch of all the libraries after that. Please see my question below.
@@ -17,3 +17,17 @@ repos: | |||
- id: check-yaml | |||
- id: end-of-file-fixer | |||
- id: trailing-whitespace | |||
- repo: local |
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.
Please explain how this works. I didn't look into it too deeply, but my first impression was that local
meant local to your machine. Will this still work in the library when someone PRs to it?
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.
Right, it means that it's not pulling the code that pre-commit runs from another repo, but rather, it's executing things locally.
Since part of the GitHub workflow is to install pylint, and that happens before pre-commit runs when someone creates a PR against a GitHub repository, we will be assured that pylint is installed.
The downside is that pylint isn't automatically installed as it would with pre-commit. If we want, we could add that to the custom hook, however, I know we'd rather not pollute peoples' environments by installing things willy-nilly.
Closing this issue since the root fix is addressed with PR #109 in the Cookiecutter repo. |
This add calls to
pylint
through the pre-commit hooks, instead of the GitHub workflow.This is a draft PR until the GitHub workflow actions in
build.yml
are also updated.