You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, I'd like to express my gratitude to all those involved in integrating this tool with GitLab. So far, it has been working very well.
Whenever the PR-Agent conducts code reviews with commitable_code_suggestions enabled, it generates multiple suggestions. However, upon running the PR-Agent again, there is a chance of regenerating the same suggestions. Is it possible to respond to these repetitive suggestions through a threaded approach?
The text was updated successfully, but these errors were encountered:
i am not sure what is a "thread" in github (or in gitlab ? bitbucket ?). is that something that is actually supported?
our recommended, and default way, for code suggestions is as a single comment. we introduced a lot of improvements there, including noise reduction, and are planning to keep working on that mode. commitable code suggestions are far too noisy for most users, and that's why we are not prioritizing them. Still, a contribution from the community for committable code suggestions will be welcomed
Because I noticed duplicated and similar code suggestions when using committable code suggestions, we would like to consolidate them under the same thread. This approach will help reduce clutter and streamline categorization.
commitable code suggestions are far too noisy for most users
Hello everyone,
First of all, I'd like to express my gratitude to all those involved in integrating this tool with GitLab. So far, it has been working very well.
Whenever the PR-Agent conducts code reviews with commitable_code_suggestions enabled, it generates multiple suggestions. However, upon running the PR-Agent again, there is a chance of regenerating the same suggestions. Is it possible to respond to these repetitive suggestions through a threaded approach?
The text was updated successfully, but these errors were encountered: