You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support creating workspaces from Drupal GitLab issue forks and associated merge requests #163
When creating a new workspace from a GitLab issue number, Coder DDEV incorrectly reports that no issue fork exists, even though the issue fork has already been created and push access has been granted.
Enter the GitLab issue number 3591879 in the workspace loader.
Attempt to create a workspace.
Actual result
The following error is displayed:
No issue fork exists for #3591879 yet. To work on this issue, visit the issue page on drupal.org and click "Get push access" to create a fork, then come back here.
Expected result
The workspace should be created successfully because an issue fork already exists and push access has already been granted.
In this example, creating a workspace for issue 3591879 should result in a workspace that already contains the code from MR !99, allowing contributors to review, test, and continue work immediately without manually checking out the MR branch.
Benefits
Better support for GitLab-native Drupal contribution workflows.
Faster onboarding for contributors reviewing existing work.
Reduced confusion caused by Drupal.org-specific error messages when working with GitLab issues.
Consistent workspace creation experience regardless of whether the issue is hosted on Drupal.org or GitLab.
changed the title [-]Support Gitlab issues[/-][+]Support creating workspaces from Drupal GitLab issue forks and associated merge requests[/+]on Jun 18, 2026
changed the title [-]Support creating workspaces from Drupal GitLab issue forks and associated merge requests[/-][+]Support for Drupal GitLab in Drupal Issue Picker[/+]on Jun 18, 2026
changed the title [-]Support for Drupal GitLab in Drupal Issue Picker[/-][+]Support creating workspaces from Drupal GitLab issue forks and associated merge requests[/+]on Jun 18, 2026
Activity
[-]Support Gitlab issues[/-][+]Support creating workspaces from Drupal GitLab issue forks and associated merge requests[/+][-]Support creating workspaces from Drupal GitLab issue forks and associated merge requests[/-][+]Support for Drupal GitLab in Drupal Issue Picker[/+][-]Support for Drupal GitLab in Drupal Issue Picker[/-][+]Support creating workspaces from Drupal GitLab issue forks and associated merge requests[/+]rfay commentedon Jun 18, 2026
@gxleano do you know if issue numbers still remain unique through the Drupal ecosystem ?
gxleano commentedon Jun 19, 2026
@rfay I have asked to @fjgarlin who is in charge on the Gitlab migration and he told me that they are not unique globally.
Different modules can have the same IID, but it would be unique per module. So, we could just try to make it works with
module-issue_number:ui_icons-3591879rfay commentedon Jun 19, 2026
Probably we just have to insist on the full link going forward.
rfay commentedon Jul 1, 2026
@gxleano please take a look at (and do some testing on)
fix(docs-issue-picker): require project-qualified issue input, suppor…
fix(drupal-contrib): don't trust a drupal.org node ID without checkin…
ci(drupal-contrib): add a second issue-fork test case for a migrated …
fix(docs-issue-picker): require project-qualified issue input for Git…