<!--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> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=591718) </details> <!--IssueSummary end--> The following discussion from !224052 should be addressed: - [ ] @phikai started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/224052#note_3106482405): (+7 comments) > @marc_shaw One of my thoughts around abstracting commenting here is that if we could somehow get to **ONE** interface for _ALL_ the comment types... right now we have: > > - https://docs.gitlab.com/api/notes/ > - https://docs.gitlab.com/api/discussions/ > - The version of Discussions for Diffs > - https://docs.gitlab.com/api/draft_notes/ > > The way I've been thinking about this is how do we make it easy for external tools to consume and comment (READ and WRITE) in merge requests. > > I'm not saying that needs to be the scope for this particular experiment, but I think it's what we should strive for long term here.