Add linting workflow using Black for code formatting#26
Closed
Karsten-Larson wants to merge 4 commits into
Closed
Conversation
Karsten-Larson
force-pushed
the
linting
branch
3 times, most recently
from
September 24, 2025 04:10
3bbcd0a to
c2a1e03
Compare
Karsten-Larson
force-pushed
the
linting
branch
from
September 24, 2025 04:11
2672b85 to
fcc2af0
Compare
Collaborator
Author
|
This linter is bad and ruins some of our code styling |
This file contains hidden or 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
1 participant
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.
This PR adds a GitHub action that will automatically reformat all Python code. This will ensure a consistent style throughout all our code.
This action creates a new commit if it detects any formatting changes and adds it to the current PR it detects it in. Under our current PR merge squash policy, these additional commits will not pollute the commit history.