Ah, okay! I see the distinction between these two posts.
- Updating the summary comment when there’s a change that affects the Quality Gate SonarQube-side (marking an issue as false-positive). That’s the issue you mention here: Adjust GitLab merge request decoration depending on SonarQube project status
- Using the GitLab Merge Request Approvals API to handle the QG as a “check”/'status" rather than just a comment
@Farah, I think was responding to your second point when she responded here. She and I had a little behind the scenes chat about it (this approvals API has been on my radar for a while).
I will come back to your other post.