Repository navigation
build: enforce Java formatting with Spotless - #7
Merged
Merged
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
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.
Summary
Add deterministic Java formatting with Spotless and enforce it both during Maven validation and on pull requests targeting
master.Changes
spotless:checkto Maven'svalidatephase while keepingspotless:applymanualScope and non-goals
This change affects Java formatting and its build and pull-request enforcement only. It does not change runtime behavior, generated APIs, SQL parameter or selected-column ordering, or Java text-block values.
The workflow does not run the test suite, rewrite source files, add push or scheduled triggers, introduce matrices or artifacts, configure dependency updates, or change branch-protection settings.