Do a full depth clone - #130
Merged
Merged
Conversation
This is because the CI is producing different results than an up-to-date local build, and is a workaround suggested by the spotless devs, and will probably work better because of that. It may reduce the speed of the CI builds, but there isn't much we can do about that until the spotless devs can fix it on their end.
kcooney
approved these changes
Feb 9, 2026
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.
Some issues have been popping up with spotless throwing errors in CI and not on local clones, even if
origin/mainis up-to-date. So, instead of doing a shallow clone, just do a full-depth clone like the spotless devs recommend in their docs. We could change this to do a full fetch, but it is probably just simpler to do a non-shallow clone.This also updates the action for setting up gradle (which among other things verifies the integrity of the gradle wrapper jar)