GitLab/Hosting a project on GitLab

WMF Release Engineering is collecting notes here on migrating a project from Gerrit; this may become a basis for automating at least some of this process.

See also: draft.


 * Generally, GitLab projects live in a group named for the functional area of code, under the top-level /repos.
 * Users should typically be added to the project's group, rather than the specific project
 * This gives access to a pool of CI runners.
 * There are some exceptions to this layout, where there are differences in policy around project trust.
 * /toolforge-repos
 * /cloudvps-repos

Sections to develop here:


 * How to request a namespace
 * Doing a phab form: transactions/editengine/maniphest.task/view/105/
 * Creating a new /repos group if necessary
 * Group settings
 * Make appropriate people group a member of the project group
 * Creating a new GitLab project
 * Always use  for primary branch
 * Don't use issues - these will be automatically disabled anyway
 * Don't use wikis - these will be automatically disabled anyway
 * Project settings
 * Copying the repo over (including review metadata with ).
 * Adding
 * Archiving the old project on Gerrit
 * Remove from CI
 * Update Phabricator mirroring?
 * Updating external references and docs
 * Mirroring to GitHub
 * Changing remotes on existing clones