Skip to content

comparison with forked project

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

When comparing branch based on forked project, the comparison generates based on original project not the forked project. It is also the master branch not the selected branch. This start in beginning of October 2024.

Steps to reproduce

under the code section of menu, select compare revision select a developer branch in the forked project as source.
select a developer branch in the forked project as target. select only incoming from source click compare button produces a screen suggestion it compared the forked branch with the original branch incorrectly

Example Project

https://gitlab.com/palcare/pal-base-4/-/compare

What is the current bug behavior?

incorrectly display the wrong comparison between branches. It defaults to original fork

What is the expected correct behavior?

display the changes between the 2 branches on the same fork

Relevant logs and/or screenshots

image image

Output of checks

This bug happens on GitLab.com

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

Edited by 🤖 GitLab Bot 🤖