<!--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=342736) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary While reviewing ~15 suggestions in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/71500, I selected 13 of them to apply. However, they failed to apply with ``` Suggestions are not applicable as their lines cannot overlap. ```  Raising this as a bug because of the ~UX experience. ### Steps to reproduce - Make multiple suggestions on a MR, and (I suppose) make some of them overlap. - Add them all to the batch - Try to apply them all. ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ### What is the current *bug* behavior? The conflict is raised once all the suggestions have been added to the batch. ### What is the expected *correct* behavior? Flag the conflict when the second suggestion is added to the batch. ### Relevant logs and/or screenshots <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise. --> ### Output of checks This bug happens on GitLab.com GitLab Enterprise Edition 14.4.0-pre f1930dccb0f ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->