Skip to content
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.

Triage and address static code analysis issues #22

Open
ossdhaval opened this issue May 19, 2021 · 1 comment
Open

Triage and address static code analysis issues #22

ossdhaval opened this issue May 19, 2021 · 1 comment
Assignees

Comments

@ossdhaval
Copy link
Contributor

ossdhaval commented May 19, 2021

Triage all static code analysis issues reported on Codacy
After triage, all issues that we agree to fix, should be made into project issue on appropriate Github repo.
Simpler issues should be marked 'good first issue'. This also aligns with 'CII best practices`

Benefit: Improves product stability


Due: 30th June 2021

@ossdhaval ossdhaval self-assigned this May 19, 2021
@ossdhaval
Copy link
Contributor Author

Partially achieved.
This has been taken care by having Sonar integration with PRs. PRs can only merge after it passes quality gate.

What is remaining is to triage all backlog issues and identify which issues need immediate attention ( like high risk and security hotspots ). And fix those. Keeping this issue open for now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant