Annotate merge request versions with simple descriptions

Problem to solve

In rebasing workflows people often push new versions the merge request many times, but it's hard to know what actually changed because every commit appears to have changed.

Further details

Proposal

When receiving a push to a merge request, we should compare the present version to the previous version to provide a simple description:

• @user rebased 'feature-x' on 'master' - no changes to the commit messages/authors, no changes to contents of files, this is less important from a reviewer perspective (if it was a clean rebase)
• @user reworded 2 commits - only changes to the commit messages/authors, no changes to contents of files
• @user modified 1 commit - no changes to the commit messages/authors, changes to the contents of files
• @user reordered 4 commits - no changes besides reordering

These actions could and presumably are frequently combined, so it might be difficult to make useful output.

These could then be used to annotate an improved version/commit switcher, so that is easy to spot the commits that need review.

Links / references