this is more of a general/process question.
We have an older code base where we recently introduced SonarCloud.
This has been very smooth but the we are currently discussing how we can best handle this specific scenario:
I would be very welcome over any feedback or suggestions
With the CleanCode/CleanAsYouGo approach only new additions of a pull request get nagged about.
The problem comes if somebody does some changes to a line which already includes some old issue, as this will bring up the issue as “new” for their pull request and assign it to them.
Some of those fixes include multi-line or even multi-file changes which would be out of scope for the pr.
Small issues which only affect the line, we fix directly.
Issues which are bigger will be marked as
Wont Fix) with a comment stating why.
We would then go over all
Accepted issues periodically to check if they still should be considered
- Is this the recommended approach (as this hides issues we want to fix in the future behind the
- According to the docs closed issues are up for deletion after 30 days. The docs also mention that
Acceptedissues are handled as
closed. So what happens after 30 days? Will the issue re-appear as new or will it be completely discarded?