Flow/pre commit action - upgrade pre-commit hooks #547
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
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.
@set-soft Best wishes for 2024!
I've been setting up a pre-commit github action on my projects with a script to convert the messages to code annotations on github.
I've also updated the hook versions (
pre-commit autoupdate) which reveal some new "Issues":The spelling could be fixed in this PR or a separate PR.
As far as the linter messages are concerned, it needs to be decided if they will be changed in the code or excluded in the
setup.cfg.A limited number of Github Pull Request code annotations are visible in the Summary of the workflow and in the Files changed tab of a pull request (annotations of files that were not changed are at the bottom of the tab).
I hope you find this useful