-
Notifications
You must be signed in to change notification settings - Fork 889
[core] add IDE agnostic configuration thus run spotlessApply
on dev environment
#1265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
daff237
to
97acd62
Compare
.spotless/licence.header
Outdated
@@ -0,0 +1,14 @@ | |||
/* | |||
* Copyright 2016 Google Inc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
<parent> | ||
<groupId>com.google.googlejavaformat</groupId> | ||
<artifactId>google-java-format-parent</artifactId> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this an issue having SSOT ?
<id>spotless-apply</id> | ||
<phase>process-sources</phase> | ||
<goals> | ||
<goal>apply</goal> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
disable on CI
97acd62
to
60e09f2
Compare
google seems dead. Agreement Name Date Signed Manage |
Automating Code Formatting with Spotless in Gradle
By binding the
spotlessApply
goal to local execution, we can automatically fix formatting issues during a single Gradle build when triggered for every push. This approach offers two key benefits:This pattern is already well-established in major projects:
Current Limitations and Proof of Concept
While the concept is proven in Maven environments, Gradle/Spotless integration currently requires additional configuration: