Enable Spotless formatting for Groovy files - #87
Open
wborn wants to merge 2 commits into
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
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
This enables GrEclipse formatting for Groovy files as part of the Spotless configuration.
The second commit applies Spotless formatting to the Groovy files.
Merge
The two commits should preferably remain separate:
To preserve this separation, the PR should preferably be rebased/merged with the merge queue temporarily disabled rather than squashed.
After merging, the resulting SHA of the Format Groovy files commit can be added to
.git-blame-ignore-revs, so the repository-wide formatting changes do not interfere withgit blame.Similar to openremote/openremote#3215