Deal with write conflicts

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

GitLab currently ignores write conflicts, which is bad from my point of view, because it makes one look like a fool unnecessary and it also breaks history comments. Other tools like bugzilla deal with write conflicts more gracefully, it notifies me that someone else made a comment which I didn't see before I started my comment and it lets me choose what to do.

Consider a scenario like this:

• Someone writes a mistake into the comment
• I notice it and will write "that's not true"
• but before I send it, that person will realize its mistake and will correct it with a comment I didn't see

then the result in gitlab will be (respective comments in []):

A: [ mistake ]

A: [ I'm sorry, I meant something else ]

C: [ that's not true ]

Who's gonna look like a fool here? Bugzilla doesn't let me do this without warning me first.