<!--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=520363) </details> <!--IssueSummary end--> As part of reviewing the docs change in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/182013, I asked myself "why don't we use the word **rebase** in the system note when a user triggers a rebase from the UI?" We can't always know _from Git_ if a push contains a rebase, but if the user triggers the `/rebase` quick action or chooses to rebase from the UI, we _do_ know. It'd be nifty if the system notes reflected the difference. Right now, they don't:  The system note for rebases from the UI add two extra words: `[user] rebased and added [$num] commits [$timeago]`. This would also improve the UX a tiny bit for the forgetful among us (hi, it me) who often wonder "did I intend to rebase and forgot, or did I really do it?" ## Related issues Related to https://gitlab.com/gitlab-org/gitlab/-/merge_requests/182013+ which finally made me ask the question