
Ben Gamari
Herbert Valerio Riedel
writes:
...
I wonder too how this is represented in GitLab... especially when a MR is comprised of multiple commits, and those individual commits evolve, might get reordered, commits added or removed fromt he stack, or when the whole MR gets rebased in the process...
To be clear, GitLab saves each head commit that you push to an MR branch. These iterations are known in the review interface as "versions". The review interface then allows you to view differences between either
a. any two versions b. any version and the target branch (e.g. master)
Unfortunately (but perhaps not unexpectedly) this scheme does not deal well with changes due to a change in base commit (as would happen in the case of rebasing). It appears that GitLab must just run `git diff` between the two heads when asked to compare two versions of a MR.
It sounds as though this is something on upstream's radar as something to improve upon in the near future [1]. Cheers, - Ben [1] https://gitlab.com/gitlab-org/gitlab-ce/issues/23269