-
Notifications
You must be signed in to change notification settings - Fork 23
Enhance changelog job with more validation steps #44
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
Conversation
gravesm
left a comment
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.
What's the difference between this PR and the existing changelog workflow? Can we work with the network team to try and incorporate these changes into the other workflow?
The existing workflow has been updated |
gravesm
left a comment
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.
Could you describe how this is different from the current solution? There are likely people already using the existing action and if this changes the behavior we need to know how it is changing.
Qalthos
left a comment
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 think I'm convinced that this does what is needed more precisely than before, though it is a great deal more complicated now. I think we can merge this, but I would love @cidrblock's eyes on it as well.
|
I think this is fine, although in the case of a failure (sys.exit(1)) I'd like to see a bunch of debug level information printed out about what happened during the run. Doc strings, type hints, black and pylint/flake8 erros resolved. Here's some I found with a quick run: |
|
minor comment, isort is helpful to get consistency across projects for the import statement, this is the recommandation based on my local config |
if all these check are performed we need to introduce them as a workflow for this repository |
Yes, absolutely. This is the first Python file in the repo, so we should definitely be using this opportunity to set some checks. |
|
@Qalthos please try to suggest a commit and do not push the commit directly to the PR, otherwise, it is a pain to rebase it locally if there is a local modification |
|
@Qalthos why using another ci system for this repository instead of GitHub actions? |
Only because it was already set up, just not enforcing or checking Python files. It's not necessarily a complete or permanent solution, and the fact that it fails to autofix issues in workflows is an unexpected pain, so may require a revisit. |
Qalthos
left a comment
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.
This adds mypy, flake8, and pylint checking, which should match @cidrblock's previous comment. Errors don't look too arduous to implement, but let me know if there you have any concerns.
Co-authored-by: Kate Case <[email protected]>
Co-authored-by: Kate Case <[email protected]>
for more information, see https://pre-commit.ci
|
@Qalthos pull request is ready for merge |
Qalthos
left a comment
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.
Looks good otherwise.
Co-authored-by: Kate Case <[email protected]>
Co-authored-by: Kate Case <[email protected]>
Co-authored-by: Kate Case <[email protected]>
for more information, see https://pre-commit.ci
This changelog validates that the PR contains a valid changelog file if needed.