Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
Link to the issue fork on an issue page is a 404.
Steps to reproduce
1. Go to an issue and click 'create issue fork'
2. Click the link 'Issue fork drupal-2795567' with URL https://git.drupalcode.org/issue/drupal-2795567
3. It takes me to https://git.drupalcode.org/issue/drupal-2795567/-/import which is a 404
The 'create new branch' link has the same problem -- the link URL is https://git.drupalcode.org/issue/drupal-2795567/-/branches/new?branch_na... but I get taken to https://git.drupalcode.org/issue/drupal-2795567/-/import
After 5 minutes or so it works ok.
Proposed resolution
Looks like gitlab isn't catching up in time? Is there a way for the d.org UI to check when gitlab is ready?
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork drupalorg-3189329
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
drummYes, there is an “import” process GitLab goes through after the initial project creation, which can take a few seconds.
I did add some polling for this in the front-end with #3155690: Add new branch on issue fork creation. We should be able to extend this to hide or disable the links until ready.
Comment #5
drummThis is now deployed along with https://git.drupalcode.org/project/bluecheese/-/commit/376c99948c1204d17.... Until forking is completed, the links are now greyed out or hidden.