The finding description is currently geared towards proper audit findings. We need to add a finding type code quality that has a simpler description.
For writing to GitHub, rather than create a new issue for each CQ finding, it should write all CQ findings to a single issue. This may require another field in the repository configuration that keeps track of which issue is currently storing the CQ findings. If no CQ issue exists, a new one should be created, whereas if one exists, the finding should be added as a new comment in this issue. Preferably this is purely done through a link as is currently done for creating new issues based on findings.
The finding description is currently geared towards proper audit findings. We need to add a finding type code quality that has a simpler description.
For writing to GitHub, rather than create a new issue for each CQ finding, it should write all CQ findings to a single issue. This may require another field in the repository configuration that keeps track of which issue is currently storing the CQ findings. If no CQ issue exists, a new one should be created, whereas if one exists, the finding should be added as a new comment in this issue. Preferably this is purely done through a link as is currently done for creating new issues based on findings.