<!--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=521929) </details> <!--IssueSummary end--> Currently, a code suggestion is bound to a version of a merge request, meaning, when the surrounding code changes, the code suggestion is marked as outdated, no matter if it _could_ potentially still be applied, because it might not. There's no way to try to apply the suggestion. It would therefore be nice to have an option to either * Resubmit the suggestion for the new version * Try to apply the suggestion anyway and then resolve merge conflicts (if there are any) Furthermore, it would be awesome, if the reviewer could get a similar notification when their suggestion is outdated to the one, the assignee gets when the branch as merge conflicts with the target branch