OneLiteFeatherNET / OneLiteFeatherNET/Voyager
ci: add Gradle checkstyle/lint step to build pipeline
Open
Nobody has claimed this yet.
ci
enhancement
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 12
Description
`build.yml` only runs `./gradlew build`. There is no static analysis step. Adding explicit lint enforcement ensures code style violations fail the CI pipeline.
Acceptance criteria:
- Checkstyle or SpotBugs configured in Gradle
- CI fails on violations
- Existing code passes the configured rules
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with build.yml and the repository's Gradle configuration to understand how ./gradlew build currently runs. Identify where Checkstyle or SpotBugs can be configured and how the CI job should invoke it. Done means a static-analysis tool is configured, violations fail CI, and the existing code passes the selected rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- build-system, ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100