Remove code formatting check during Travis CI build #91
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
…daily work (always leading to additional 'code formatting' commits at the end of PRs
per1234
approved these changes
Feb 21, 2020
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.
Hi @per1234 👋 With this PR I intend to remove code formatting check from the Travis CI build because it just proves to be troublesome in the daily work (always leading to additional "code formatting" commits at the end of PRs). Now I know I was a strong supporter of this in the past but as long as not everyone working on this repository adopts a pre-commit auto-code-formatting hook (even I am guilty of not doing it) it will always lead to a polluted git history with a "let's fix this code formatting" commit at the end of every PR. If it's okay with your I would remove this check then.