>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3152637. --> Reported by: [hestenet](https://www.drupal.org/user/54034) >>> <div class="note-warning"> <h2><strong>Issue Forks and Merge Requests are scheduled for general availability on all projects on Nov 10, 2020.</strong></h2> </div> <p>We're very excited to report that we're now very close to opening up a beta test of merge requests integrated with Drupal.org issues.</p> <p>Stepping back for a moment, let's remember the ideal contribution flow that we defined when evaluating our Developer tool options:&nbsp;</p> <p class="center"><img alt="Drupal Flow" height="474" src="https://www.drupal.org/files/drupal-flow-diagram.png" width="569"></p> <ul> <li>The issue itself should remain a single-threaded conversation for discussing the particular problem to be solved.</li> <li>Every issue will be associated with one canonical issue fork(with multiple branches, as needed) which can be collaborated on by any contributor, and merged by a project maintainer.</li> <li>Contributors will be able to modify the code in these issue forks by: <ul> <li>Checking out the code and committing/pushing changes to the workspace.</li> <li>Inline editing files using GitLab's web interface.</li> <li>Legacy: uploading a patch.</li> </ul> </li> <li>All types of contribution&mdash;whether merge requests or the legacy patch workflow&mdash;will continue to trigger DrupalCI testing.</li> <li>Issue forks can be rebased (manually or automatically) when needed to resolve conflicts with upstream commits.</li> <li>Contributors and project maintainers will be able to comment on individual lines of code.</li> </ul> <p>The foundation for this work is the ability to create these issue forks from an issue on Drupal.org. This involves building an interface from Drupal.org that creates an issue fork in GitLab associated with the Drupal.org issue, and then any Drupal.org user can push to that fork and branches within it. Maintainers may then merge this work from a branch on the issue fork the project.</p> <p>That foundational work to create the necessary git hooks and access control management is now complete.</p> <h3><strong>The next steps are:</strong></h3> <ul> <li><a href="https://www.drupal.org/i/2488266">Exposing the UI for issue forks and branches on Drupal.org issues</a>.</li> <li><a href="https://www.drupal.org/i/3071681">Deciding what information to display about activity on issue forks and branches</a>.</li> <li><a href="https://www.drupal.org/i/2205815">Enabling users to open merge requests from their issue forks and branches</a>.</li> <li><a href="https://www.drupal.org/i/3071755">Deciding what activity to post back as comments to the issue queue</a> (i.e: merge request open, new activity on merge request, merger request closed, etc).</li> </ul> <h3><strong>When will merge requests be available to the community at large?</strong></h3> <p>Creation of issue forks is now available to a limited subset of projects this week. Over the course of the next several weeks, we hope to implement the additional UI features that will display relevant information about the issue forks back in the Drupal.org issue, and ultimately allow merge requests themselves.</p> <p>We hope to have the beta of merge request functionality available to some projects no later than DrupalCon Global, in Mid-July. From there, we'll work through feedback from our beta testers, and work with Drupal core maintainers, to enable issue forks for all projects in the coming months</p> <h3><strong>How can you get involved</strong>?</h3> <p>As a module maintainer, please leave a comment on this issue with the list of your project shortnames that you'd like to opt-in.</p> <p>Please note that not all projects will necessarily be selected for the beta trial.</p>