Cherry-pick via web UI picks into wrong project/repo
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
Cherry-picking (via web UI) picks into the wrong project/repo.
Steps to reproduce
- open apparmor/apparmor!1822 (merged)
- click "Cherry-pick"
- verify that "pick into project" is set to
apparmor/apparmor(default value, no change needed) - select branch
apparmor-4.1 - un-tick "Start a new MR"
- click "Cherry-pick`
What is the current bug behavior?
The changes from the MR got picked into cboltz/apparmor (where the MR initiallly came from)
What is the expected correct behavior?
The changes should be picked into the selected project apparmor/apparmor.
Output of checks
This bug happens on GitLab.com
Possible fixes
GitLab.com did the cherry-pick as expected until some weeks ago. I first noticed the wrong cherry-pick target on 2025-10-06.
The last successful/working cherry-pick I did was on 2025-08-25 in apparmor/apparmor!1766 (merged)
Therefore reverting the changes done or deployed between these dates that broke cherry-pick should help to fix this.
@gitlab-bot label typebug` @gitlab-bot label reproduced on GitLab.com