MR creation page shows “Changes: 0” instead of correct count

Summary

During merge request creation, the changes tab shows 0 even when file changes are already detected and listed.

Steps to reproduce

  • Create a branch with one or more file changes
  • Open new merge request
  • On the MR creation page, observe the top navigation

Example Project

Reproduced across multiple repositories during merge request creation

What is the current bug behavior?

The changes tab displays 0 during MR creation, despite files being listed under the files section.

What is the expected correct behavior?

The changes tab should show the correct change count, once files are detected.

Relevant logs and/or screenshots

Screenshot attached showing file changes present while changes count is 0. image image

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

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by 🤖 GitLab Bot 🤖