Codechange: fix indentation #23
Open
Conversation
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
certator
force-pushed
the
fix-indentation
branch
from
0e0b183 to
4fd4a9c
Compare
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.
Description
PEP8 guideline recommends using 4 spaces - I updated python files to comply with that.
Additionally I noticed tests fail because of missing author, I added
git config --local user.email ...commands to fix it.Context
We can extend hooks to support more use cases, in particular detecting terms which shouldn't be used in codebase - see related discussion in Discord. This is a pre-requisite step to give some minimal love to hooks, before actually proceeding further.