make pylint output more easily accessible in CI/CD
#138
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
i want to see if i can get pylint to run as a sep step. update workflow calls to reflect whats in the `conda build` target `meta.yml`
pylint feedback
quick clean up edit
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
this runs
pylintas part of theconda env createcheck, in a separate workflow fromconda buildroutines. it lets thepylintfeedback be accessed with a single click- see checks on this PR!Checklist before requesting a review
- [ ] I tried to comment my code- [ ] I wrote a new test, if applicable- [ ] I wrote new instructions/documentation, if applicable- [ ] I ran pytest and inspected it's output