DrupalCon Barcelona 2015: Pull requests are coming to Drupal.org
In the past few years there were numerous conversations in the community about the need to improve issue queues and Git workflow on Drupal.org. Suggestions ranged from implementing pull requests to migrating to a different self-hosted solution, such as GitLab, or 3rd-party site, such as GitHub. Meanwhile, new technical solutions have emerged for some of the challenges we are facing. One of them is issue workspaces.
Issue workspaces
They are a modernized version of our current workflow, which maintains the collaborative data model Drupal community uses.
They are very similar to “per-issue repositories”.
They make it possible to add support for pull requests and inline code editing in issues.
As a bonus, we can build it so that the patch process doesn’t break. This means no loss in project velocity while people learn the new tools.
In this session we will explain what issue workspaces are, and how they can be implemented on Drupal.org to improve our issue queue and Git workflow.
Issue workspaces
They are a modernized version of our current workflow, which maintains the collaborative data model Drupal community uses.
They are very similar to “per-issue repositories”.
They make it possible to add support for pull requests and inline code editing in issues.
As a bonus, we can build it so that the patch process doesn’t break. This means no loss in project velocity while people learn the new tools.
In this session we will explain what issue workspaces are, and how they can be implemented on Drupal.org to improve our issue queue and Git workflow.