Reminder to all repository users: Please do not add , commit and push any data files to your remote git repositories. The disk space the Git server is limited, it wasn't dimensioned to host anything else than code. Solely your code files need versioning. The data inputs/outputs don't. A good idea is to do "git add" individually on each file you want to commit, to avoid versioning unwanted content.

Merge requests versions

Notes:

  • Introduced in GitLab 8.12.
  • Comments are disabled while viewing outdated merge versions or comparing to versions other than base.
  • Merge request versions are based on push not on commit. So, if you pushed 5 commits in a single push, it will be a single option in the dropdown. If you pushed 5 times, that will count for 5 options.

Every time you push to a branch that is tied to a merge request, a new version of merge request diff is created. When you visit a merge request that contains more than one pushes, you can select and compare the versions of those merge request diffs.

Merge request versions


By default, the latest version of changes is shown. However, you can select an older one from version dropdown.

Merge request versions dropdown


You can also compare the merge request version with an older one to see what has changed since then.

Merge request versions compare


Every time you push new changes to the branch, a link to compare the last changes appears as a system note.

Merge request versions system note