ADFA-2522: Run spotlessCheck in CI for pull requests

[Daniel-ADFA]

• Add a Run spotlessCheck step to the build_apk job in debug.yml, immediately after the APK is assembled

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

_{Tip: disable this comment in your organization's Code Review settings.}

[coderabbitai]

Warning

Review limit reached

@hal-eisen-adfa, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fe9bfd2a-d597-4d78-8078-9bf315b33eba

📥 Commits

Reviewing files that changed from the base of the PR and between 94bb0a3 and 873bcda.

📒 Files selected for processing (1)

• .github/workflows/debug.yml

📝 Walkthrough

Walkthrough

The Android APK debug workflow now runs spotlessCheck before subsequent build and deployment steps, reporting formatting violations and failing the job when they are found.

Changes

APK Formatting Verification

Layer / File(s)	Summary
Add APK formatting gate .github/workflows/debug.yml	The workflow runs ./gradlew spotlessCheck under flox activate and exits with an error when formatting violations are detected.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• appdevforall/CodeOnTheGo#1492: Both changes modify the APK build workflow around Universal APK build steps.

Suggested reviewers: itsaky-adfa

Poem

I’m a bunny with tidy ears,
Formatting checked before builds appear.
Spotless hops through every line,
Errors thump when things aren’t fine.
Then APKs safely cross the gate.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the CI change adding spotlessCheck for pull requests.
Description check	✅ Passed	The description is directly related to the changeset and describes the new spotlessCheck step.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ADFA-2522

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}