Repository navigation
ci: Skip Spotless in the Build job - #6693
Merged
Merged
Conversation
Co-Authored-By: Nelson Osacky <nelson.osacky@sentry.io>
Contributor
PR risk: not classifiedFor commit The last run ended with status |
📲 Install BuildsAndroid
|
romtsn
approved these changes
Nov 20, 2026
runningcode
marked this pull request as ready for review
November 20, 2026 13:00
runningcode
requested review from
0xadam-brown and
runningcode
and removed request for
a team
November 20, 2026 13:00
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.
📜 Description
make preMerge, which theBuildjob runs, now runs./gradlew check -x spotlessCheckinstead ofmake check. This drops the ~420 Spotless tasks thatcheckpulls in across modules and leaves the rest of the task graph unchanged.make checkstill runs Spotless locally.💡 Motivation and Context
The
Format Codeworkflow already runsmake formaton every PR and commits any formatting changes, soBuildwas checking the formatting of the same code a second time. This takes work off theBuildjob, which is running out of resources.Format Coderuns onpull_requestonly, so pushes tomainno longer get a Spotless check. Those commits went through a PR first.#skip-changelog
via no.
--
View Session [Sentry]