Enforce formatter #490
Merged
Enforce formatter #490
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
maartenvanvliet
force-pushed
the
issues/enforce_formatter
branch
from
60c5d68
to
d721598
Compare
Output elixir version
maartenvanvliet
force-pushed
the
issues/enforce_formatter
branch
from
d721598
to
b444415
Compare
snewcomer
approved these changes
May 12, 2019
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.
The Elixir formatter was applied several months ago (4d2f943) but there was no check added in CI to ensure new commits are also properly formatted.
This PR reformats the code that was not properly formatted since the commit, and it adds a check in CI to error when a new commit introduces code that was not formatted.