Enabling issue forks and merge requests for all Drupal.org hosted projects

Issue forks and merge requests will be enabled for all projects on Tuesday, November 10th, 2020.

The Drupal.org engineering team has built an integration between the Drupal.org issue queue and our back-end git hosting in GitLab, to enable a complete merge request workflow. Beta testers from contrib and core have been helping the DA test these features since DrupalCon Global in July of 2020.

For any issue on any project on Drupal.org, the following features are enabled:

• An issue contributor can create an issue fork
• Any other contributor can be granted access to the same issue fork or start a new one
• Any contributor can then use the built in GitLab tools like WebIDE, code review, etc to contribute
• Activity in GitLab will be posted back to the Drupal.org issue stream
• When contribution is complete, maintainers can use the new issue queue merge button

At the same time - the existing patch workflow will also continue to be available, to avoid disrupting any work-in-progress.

Documentation for issue forks and merge requests is available on Drupal.org:

• Contributor docs for creating forks and merge requests: https://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupa...
• Maintainer docs for reviewing and merging merge requests: https://www.drupal.org/docs/develop/git/git-for-drupal-project-maintaine...
• Drupal.org docs about implementation of merge requests: https://www.drupal.org/drupalorg/docs/gitlab-integration/issue-forks-mer...

Live previews for core issues

• For core issues specifically, contributors will have the option to spin up live previews of a Drupal site with the merge request changes automatically applied.
• These previews are generated using TugboatQA, the same infrastructure underlying SimplyTest.me