The new issue forks functionality is going to be awesome.

This past Sunday I did a livestream where I tried out the new issue forks functionality on Drupal.org. The feature is currently beta and project maintainers need to opt-in for the functionality. At the moment you can create a repository fork for an issue, create a work branch, and commit to that branch. You will need to manually create a patch to be uploaded, as Merge Requests with Drupal.org issues are still being worked on (the Drupal Association Infrastructure team is hoping to have this available for DrupalCon Global!)

When you view an issue that supports issue forks, there will be a new block in the sidebar. This allows you to create an issue fork or view information about the existing fork and its branches.

To work on an issue fork you need to grab the Git URL information and add it as a remote repository to your existing local repository — or you can just clone it directly!

One thing I wish it provided was the full Git command to add as a remote or clone. Everyone should have an SSH key with their Drupal.org account, so I think they could exclude the HTTPS Git remote URL field for the command field.

I had to run the following command to get the issue fork locally and contribute to it

git remote add commerce-3150917 git@git.drupal.org:issue/commerce-3150917.git

Another gotcha is that creating an issue fork does not automatically create a working branch for the issue fork. In the…