Making a change in the Single File Editor does not create a new MR version when there is a change to previous version but not to master
Summary
I create a MR by changing a file in the Single File Editor, creating a new branch and MR in the same step. Then I visit that MR, open the Single File Editor again to revert that change and make another commit.
- Expectation: The MR would now have two versions
- Reality: The MR only has one version
The diff view shows correctly that there are no changes. However, because I'm curious I open the second dropdown and check out what information "Latest version" shows.
- Expectation: "Latest version" has the newer commit attached to it
- Reality: "Latest version" has the first commit attached to it
I'm not sure in which other situations a version might not get created, as it seems to work in other scenarios, so I'm not going to assign a severity until we have figured out under which circumstances it's broken.
Steps to reproduce
Example Project
What is the current bug behavior?
What is the expected correct behavior?
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
/cc @pedroms