Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Once #3071473: Add a create fork / workspace button to issues is done, we likely want to have a button to create a branch / have this combined with the initial create issue fork.
If combined with creating the issue fork, we’ll need some polling, webhooks, or other duct tape to create the branch once the fork is ready. Forking is not instantaneous.
A UI for this will encourage using branches with consistent naming. Having a good UI for what to branch off of may be a decent amount of work.
(Skipping this and having contributors always make their own branches via GitLab or Git CLI is an option, maybe not a good one.)
Issue fork drupalorg-3071746
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:
compare
Comments
Comment #2
hestenetI would tend to agree that having a button/ui from the issue is a good architectural decision to encourage consistency in naming.
Not sure it needs to be combined with making the issue fork - the button could be displayed only after fork creation, perhaps.
Comment #3
hestenetComment #4
drummI’m planning to do a simple link to GitLab’s new branch form. GitLab’s UI for choosing “Create from” isn’t something we need to try to replicate, even though we could maybe put in some smart suggestions.
We can pre-fill
{issue nid}-for the new branch name. We can also pre-fill ref to the issue’s branch. And maybe add “new branch from here” links to each branch later.Comment #5
drummComment #7
drumm