Migrate gitlab-ui into design.gitlab.com repository

  • @markrian will implement this phase.
  • Subsequent phases depend on this.

In order to minimise disruption to development, the transition from gitlab-org/gitlab-ui> to a monorepo needs to happen quickly. We don't want to block changes on gitlab-org/gitlab-ui> for long, and we also don't want to have to sync changes from gitlab-org/gitlab-ui> to gitlab-org/gitlab-services/design.gitlab.com> repeatedly. Here's how I see this working:

  • Prepare a script and/or series of patches that performs the merging of the repositories. How this script/series of patches works will be informed by Phase 1.
  • Once confidence in the approach is high (i.e., after reviews and test runs of it are acceptable), announce widely a "merge day", during which:
    1. The gitlab-org/gitlab-ui> repository will be locked and marked for archival. This means no new merge requests, issues, or repo pushes.
    2. The script/series of patches will be applied to merge gitlab-org/gitlab-ui> into gitlab-org/gitlab-services/design.gitlab.com>
  • The announcement would also include information about changes to workflows, including:

Once that's done, we'll still have working @gitlab/ui releases being created by the gitlab-org/gitlab-services/design.gitlab.com> repository.

Post-merge things to address

Edited by Mark Florian