<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=537536) </details> <!--IssueSummary end--> # Situation Suggestions are a good way to do code review, however, when having more complex scenarios (#29700, #537531, #521929, #454339, etc.), they have their shortcomings # Solution Don't create suggestions as comments but * Create a new branch * if it's the reviewers first suggestion * or if the reviewer wants to start a new set of conflicting changes * Create commit on said branch * Link the commit to the comment/MR in the UI * When applying the suggested change, the assignee might be offered two options: * Cherry-pick the specific commit * Merge the whole branch into the MR's branch # Benefits * :white_check_mark: Author, co-author, and committer information is correctly tracked via git (#526258) * :white_check_mark: Commit message is correctly tracked via git (#518632) * :white_check_mark: Pipelines would run for each suggestion (#35572) # Related &832