-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Labels
enhancementNew feature or requestNew feature or requestjavaPull requests that update Java codePull requests that update Java code
Description
Problem
Codacy provides redundant static code analysis that overlaps with SonarCloud and CodeQL. This creates noise, slower CI runs, and maintenance overhead for duplicate tooling. We only need Codacy's coverage reporting, which Codecov already handles more effectively.
Proposed Solution
Remove Codacy integration entirely while maintaining our existing quality and security coverage through:
- CodeQL: Security vulnerability scanning
- SonarCloud: Code quality and technical debt analysis
- Codecov: Code coverage tracking and visualization
Suggested Approach
-
Remove configuration files
- Delete
.codacy.yml
- Delete
-
Update documentation
- Remove Codacy badge from
README.md - Update any references to Codacy in documentation
- Remove Codacy badge from
-
Clean up CI/CD workflows
- Remove Codacy steps from
.github/workflows/*.yml(if any) - Remove Codacy-related secrets/tokens from repository settings
- Remove Codacy steps from
-
Archive Codacy project (optional)
- Remove or archive the project from Codacy's dashboard
- Revoke GitHub integration permissions
Acceptance Criteria
-
.codacy.ymlfile is deleted - Codacy badge removed from README
- No Codacy references in GitHub Actions workflows
- CI pipeline runs successfully without Codacy
- CodeQL, SonarCloud, and Codecov continue working normally
References
- Existing quality stack: CodeQL (security), SonarCloud (quality), Codecov (coverage)
- Codacy dashboard: https://app.codacy.com/
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestjavaPull requests that update Java codePull requests that update Java code