Skip to content

Document how to run style/static-analysis checks locally - #4452

Draft
arnaud-lacurie wants to merge 1 commit into
mainfrom
apple/arnaud-lacurie/document-style-checks
Draft

Document how to run style/static-analysis checks locally#4452
arnaud-lacurie wants to merge 1 commit into
mainfrom
apple/arnaud-lacurie/document-style-checks

Conversation

@arnaud-lacurie

Copy link
Copy Markdown
Collaborator

Summary

  • Adds a "Style / static analysis checks" section to the using-gradle skill: the CI-parity
    command (matching .github/workflows/pull_request.yml's style job), report locations,
    and a couple of common Checkstyle/PMD violations that show up when hand-resolving merge
    conflicts (redundant same-package imports, unnecessary fully-qualified names).
  • Adds a PR Workflow reminder in AGENTS.md to run these checks before pushing.

Motivated by hitting exactly these violations while manually rebasing a stack of PRs across a
few months of upstream drift — nothing in the skills documented how to reproduce CI's style
check locally, so it wasn't caught until CI ran.

Test plan

  • N/A — documentation only

Adds a "Style / static analysis checks" section to the using-gradle
skill (CI-parity command, report locations, common violations seen
when hand-resolving merge conflicts) and a PR Workflow reminder to
run it before pushing.
@arnaud-lacurie arnaud-lacurie added the documentation Documentation change label Aug 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Documentation change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant