Duo + Q /q review adds threads that should be comments
Summary
Using Duo with Amazon Q /q review opens multiple threads for items that should be comments. Many customers require that all threads be resolved before it can be merged.
Steps to reproduce
- Create a new Project that has Duo with Amazon Q enabled.
- Create an MR, that includes some commits (preferably that would include something that would be reviewed by Amazon Q)
- Run
q /reviewvia a comment.
Example Project
What is the current bug behavior?
The starting and finshed comments are threads.
What is the expected correct behavior?
These items should be comments rather than threads.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: \\\`sudo gitlab-rake gitlab:env:info\\\`) (For installations from source run and paste the output of: \\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:check SANITIZE=true\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\`) (we will only investigate if the tests are passing)
Possible fixes
Patch release information for backports
If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.
Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.
High-severity bug remediation
To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.