<!--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=27013) </details> <!--IssueSummary end--> Pushing changes to merge request will create a new system note, which is great! We should be smarter about how we render these notes. For example, if **the same user** pushes more changes to the merge request over a few hours or days without any activity, we can summarize the system notes so that the timeline is easier to read. ### Proposal Summarize push system notes if: 1. pushes come immediately after each other - no any other events between them 1. pushes lay in a small time window (1 minute - 30 minutes) ### Links / references