Closed (duplicate)
Project:
Drupal.org infrastructure
Component:
GitLab
Priority:
Normal
Category:
Plan
Assigned:
Reporter:
Created:
8 May 2019 at 00:19 UTC
Updated:
3 Feb 2022 at 15:47 UTC
Jump to comment: Most recent
Now that GitLab powers some of the core repository functionality on drupal.org, with the completion of Phase 1 at the end of March 2019, it's time to identify priorities for Phase 2. This will serve two purposes:
Comments
Comment #2
hestenetThanks for creating this issue @DamienMcKenna - I'll work on updating the issue summary and finding any child issues that may already exist.
Comment #3
hestenetComment #4
hestenetComment #5
hestenetComment #6
andypostActually deduplication released 2 weeks ago in https://about.gitlab.com/2019/07/22/gitlab-12-1-released/#git-object-ded...
Comment #7
drummI recently took some time to plan out child issues of #2488266: [META] Improve Git workflow on Drupal.org by implementing issue workspaces and #2205815: Merge requests in Drupal.org issue queues?, including some further testing and research needed as we work on things, and some discussion points. Those are the best issues to follow progress in.
Comment #8
volegerMeanwhile, there is a great initiative on how the contrib extensions can live at gitlab.com https://twitter.com/weitzman/status/1262775567386136577 .
Any news regarding Phase 2?
Comment #9
hestenetWe had a bit of a table-flip of our roadmap in the first part of this year when we pivoted to support #DrupalCares fundraising and developing a virtual conference platform. That said, I believe we're getting close to getting back to this feature - and I'll try to prepare a blog post for when we make it available as a beta to first projects. Thanks for checking in @voleger
Comment #10
andypostLooks except evaluation of gitlab-ci this issue complete
Comment #11
volegerLinking the related issue
Comment #12
drumm#3227737: [Meta] GitLab Acceleration Initiative is probably the best place to track the next steps for Drupal’s GitLab use.