 The Drupal Association is pleased to announce a partnership with GitLab to update the developer tools on Drupal.org. We'll be rolling out this project in three phases. In the first phase, we'll be integrating GitLab's code viewing and code review tools into Drupal.org. As you can see here, you can view commits in the GitLab interface, scroll through the diff, and add comments. In the second phase, we'll be enabling merge requests in inline editing. In this example, you can see a new branch being created from the Drupal.org issue queues. This branch will be made available for collaboration in the GitLab interface by multiple Drupal contributors. In this first example, you can see a user navigating the branch to edit a file without having to clone a local copy. These edits can be committed back to the branch and a comment will automatically be posted to the issue queue indicating the changes that were made. If another user wants to make changes, they could open another branch, but because Drupal prides itself on collaboration and single-threaded contribution, they can also work on the same branch to continue the work of the initial contributor. In this example, we now see a new user using the inline editor to make an additional edit or correction to the first user's contribution. Once those changes are committed, they're again published back to the issue queue. When one of the collaborators decides that they're ready for the changes to be merged, they can open a merge request from a button on the issue queue. This merge request is automatically generated in GitLab and available for review by other collaborators or by the project maintainer. Again, a comment is automatically posted to the issue queue to notify all followers that a merge request has been opened. Next step is for the maintainer to review the issue. When the maintainer signs in, they can view the merge request from the link next to the branch name in the issue, and when they decide the code is ready to be merged in, they can simply use the merge button in the GitLab interface. If necessary, they can revert the merge from the GitLab interface, or they can go to the issue to see that a final comment has been automatically posted indicating that the changes have been merged. This completes the cycle of contribution using the Drupal.org and GitLab integration. In the third phase of this initiative, we'll be evaluating additional features like GitLab's Web IDE, contribution graph, and CINCD pipelines. All these changes are coming soon, so keep an eye on the Drupal.org blog.