Reviewer/Developer decide what thread should be blocking of a Merge Request
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Currently you are able to prevent merge requests from being merged until all threads are resolved, but this presents questions as what's the difference between a thread and a comment, as a comment is considered a thread when that setting has been applied. With this use case all threads (comments) would need to be reviewed even though some comments could be trivial and not impact the code
Intended users
Proposal
Consider having the developer or reviewer decide what/which thread should be merge blocking rather than the all or none approach. I believe this would increase the speed and efficiency of the code review process for all parties involved.
Links / references
Edited by 🤖 GitLab Bot 🤖