Active
Project:
Drupal.org infrastructure
Component:
GitLab
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
17 Mar 2026 at 18:45 UTC
Updated:
25 Mar 2026 at 19:49 UTC
Jump to comment: Most recent, Most recent file
The 'view open merge request' button on the 'compare revisions' gitlab page has an incorrectly derived url, which leads to a 404.
Visit a repository page for an issue fork

The 'view merge request' button has the correct url project/gitlab_templates_downstream/-/merge_requests/66 to get to the MR

But on the 'compare revisions' page for the same MR, the 'view open merge request' button url is incorrect.

It has the issue fork part issue/gitlab_templates_downstream-3571809 instead of the canonical project part project/gitlab_templates_downstream and so
issue/gitlab_templates_downstream-3571809/-/merge_requests/66 results in a 404.

| Comment | File | Size | Author |
|---|---|---|---|
| view open mr - 1 from repo.png | 649.42 KB | jonathan1055 | |
| view open mr - 2 from repo is OK.png | 296.46 KB | jonathan1055 | |
| view open mr - 3 from compare.png | 771.81 KB | jonathan1055 | |
| view open mr - 4 from compare fails.png | 209.78 KB | jonathan1055 |
Comments
Comment #2
jonathan1055 commentedThis issue was raised in response to the request in this slack thread
Comment #3
jonathan1055 commentedOn the slack thread, @hestenet said "... describe the pattern"
Do you mean that you can do dynamic redirects, and you'd like me to work out the regex pattern and replacement. Yes I can try to do that, if that is what you meant.
Comment #4
drummWhile we can do some redirects before requests hit GitLab, we don’t really want to get into the business of trying to work around GitLab.
I don’t see the link at https://git.drupalcode.org/issue/gitlab_templates_downstream-3571809/-/c... right now, so maybe this was in an internal GitLab cache, or is it still reproducible for you? Or I could be missing something in the steps to reproduce.
Comment #5
jonathan1055 commentedThanks for the reply. Since opening this issue, that open MR has now been merged, so that must be why the button has changed. I also do not get the 'view open merge request' but instead I get 'create merge request'.
Here is the equivalent page for a MR which will not be merged just yet. It is reached via the 'compare revisions' menu item from the issue fork repository page.
The link behind the button is https://git.drupalcode.org/issue/gitlab_templates_downstream-3506685/-/m... which gives a 404
Instead of
issue/gitlab_templates_downstream-3506685it should beproject/gitlab_templates_downstreamhttps://git.drupalcode.org/project/gitlab_templates_downstream/-/merge_r... which gets to the MR correctlyComment #6
drummSince this is an upstream GitLab issue, it is best to find or make an issue for GitLab itself.
I’m not spotting an existing issue at https://gitlab.com/search?group_id=9970&project_id=278964&scope=work_ite...
If you’re filing a new issue, it is best to avoid Drupal terminology, “issue forks” are just forks for them. The best thing to have is reproducing the issue on GitLab.com itself; that also shows that it has not already been fixed upstream.
We are not on the latest version of GitLab at the moment, 18.9 instead of 18.10. That upgrade will likely happen next week.