Add and apply scalafmt #74
Merged
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
|
Done, also added the status check. |
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.
Since there are no other open PR's I think that now is a good time to add and apply
scalafmt. I used a pretty standard formatter configuration that is also the same in other sbt community plugins.@mkurz When you merge this PR either do a merge commit or rebase + merge but not squash and merge. I want to add the
Apply scalafmtcommit hash to a.git-blame-ignore-revsfile so it doesn't appear in git blame. Also once the PR is merged you can add theCode is formattedgithub action as a status check for themainbranch on PR's so you cannot merge unformatted code.