GitLab has a webhook for notes "updates", i.e. when a comment in an MR or issue is edited. Currently the code doesn't make a difference when it receives a note update or a note creation, so it appears as a new comment which seems wrong.
Logically, we should use a replacement relation to edit the first message. Firstly, that would mean that we need to keep track of the event ID for every note. Secondly, given that MR review comments are batched, it becomes a bit more complicated to construct the edit. We would need to keep track of every note that was sent in an event, and probably require to fetch the other notes in the event to have the full edit content.
We could also choose the easy way out and ignore edits.
GitLab has a webhook for notes "updates", i.e. when a comment in an MR or issue is edited. Currently the code doesn't make a difference when it receives a note update or a note creation, so it appears as a new comment which seems wrong.
Logically, we should use a replacement relation to edit the first message. Firstly, that would mean that we need to keep track of the event ID for every note. Secondly, given that MR review comments are batched, it becomes a bit more complicated to construct the edit. We would need to keep track of every note that was sent in an event, and probably require to fetch the other notes in the event to have the full edit content.
We could also choose the easy way out and ignore edits.