Add linting (code formatting) action to the PCR-GLOBWB_model master branch #38
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.
GitHub Actions are automated processes that fire during any GitHub action, such as push or pull request. I have added a GitHub action that automatically lints the code in the repository using isort for the python imports and black for the code, for any push to the master branch. It does so by automatically generating another commit with the fixes to the code.
This GitHub Action integration will help maintain a clear an structured code-base and fixes #30, fixes #29 and fixes #28 automatically (also in the future).
Possible downsides: