Option to hide empty change content commits on merge request view

Description

Proposal

Links / references

Documentation blurb

Overview

I have a compare revisions view as provided in the enclosed image 2017-09-27_1415

The patch [6143] Pass branch build target as variable does exist on both branches, but with separate change ids, due to a merge that was performed before. So effectively this commit is vacuous, as the contained change has already happened in the destination branch. Still the resp. commit is shown as part of the compare view.

Would it be possible to add a toggle button like [Hide no-change commits] where commits that will effectively NOT change anything on the target branch be hidden?

Or the other way round:

This specific commit would have change the .gitlab-ci.yml file, but this change is not visible in the inline change set view as it was already cancelled out.

Use cases

Useful for developers that have to merge between branches and only see the commits that effectively contain relevant changes.

Feature checklist

Make sure these are completed before closing the issue, with a link to the relevant commit.

Edited by 🤖 GitLab Bot 🤖