Add palantir-java-format-action into the README as a third-party integration#1706
Open
abashev wants to merge 3 commits into
Open
Add palantir-java-format-action into the README as a third-party integration#1706abashev wants to merge 3 commits into
abashev wants to merge 3 commits into
Conversation
…ub Action integration
Generate changelog in
|
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.
Before this PR
The README lists several ways to use
palantir-java-format, including the Eclipse and IntelliJ plugins, the Gradle plugin, and Spotless integration.However, it does not mention third-party GitHub Actions that wrap
palantir-java-formatfor CI formatting checks.After this PR
Document palantir-java-format-action as a third-party integration.
palantir-java-format-actionis an open-source GitHub Action that checks Java code formatting in CI using thepalantir-java-formatnative binary, without requiring Java, Maven, or Gradle on the runner. By default it only checks files changed in a pull request or push, and caches the native binary between runs.This makes it easier for users who want a lightweight formatting check in GitHub Actions CI to discover an existing integration path.
Possible downsides?
This adds a link to a third-party project that is not maintained by Palantir.