Bryan, How will this affect diffusion repositories that are already configured to mirror a remote repository? For example, https://phabricator.wikimedia.org/source/tool-xtools/ mirrors GitHub, which means there is no need for anything to be moved to GitLab. Matthew Bowker User:Matthewrb On Sep 1, 2022, at 4:26 PM, Bryan Davis &lt;bd808(a)wikimedia.org&gt; wrote: What: Diffusion git hosting moving to GitLab [0][1] When: Tuesday 2022-09-06 between 15:00 - 23:00 UTC Why: Unblocking sunsetting work for Differential/Diffusion [2] What you can do: If you have not logged into https://gitlab.wikimedia.org/ yet to attach your Developer account and look around, now would be a great time! Toolforge tool maintainers can use Striker (<https://toolsadmin.wikimedia.org/>) to create git repositories for each of their tools. Today these git repositories are hosted by <https://phabricator.wikimedia.org/diffusion/>. Starting on 2022-09-06 new repositories will be hosted under <https://gitlab.wikimedia.org/toolforge-repos> instead. We will also be migrating the 474 existing Striker created repositories from Diffusion to GitLab starting on Tuesday 2022-09-06. This process will involve making each existing Diffusion repository read-only, copying it to GitLab, and finally configuring the Diffusion repo to be a read-only mirror of the GitLab repo. We hope that this set of operations will be the least disruptive way to migrate the repositories to the new hosting platform. For tool maintainers with git repos that are migrating who *do not* yet have their Developer account attached at https://gitlab.wikimedia.org/, GitLab will send an email invitation to join the new repo. Because of some quirks of the login process that we are using for our GitLab service, the link in this email needs to be used *after* you have attached your account in order to grant you access [3]. [0]: https://phabricator.wikimedia.org/T296893 [1]: https://phabricator.wikimedia.org/T315706 [2]: https://phabricator.wikimedia.org/T191182 [3]: https://phabricator.wikimedia.org/T313366#8203450 Bryan, on behalf of the Toolforge administrators -- Bryan Davis Technical Engagement Wikimedia Foundation Principal Software Engineer Boise, ID USA [[m:User:BDavis_(WMF)]] irc: bd808 _______________________________________________ Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.… _______________________________________________ Cloud mailing list -- cloud(a)lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/ _______________________________________________ Cloud mailing list -- cloud(a)lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/

Bryan, How will this affect diffusion repositories that are already configured to mirror a remote repository? For example, https://phabricator.wikimedia.org/source/tool-xtools/ mirrors GitHub, which means there is no need for anything to be moved to GitLab.

On Thu, Sep 1, 2022 at 4:26 PM Bryan Davis &lt;bd808(a)wikimedia.org&gt; wrote: The application has been updated to create new git repositories at https://gitlab.wikimedia.org instead of in Phabricator. A few bugs have been found in the migration process for the now legacy Diffusion repos. I will continue to work through these issues during my work day tomorrow. NOTE: the "Git repositories" section of a tool's information in Striker now only displays GitHub hosted repositories. Do not panic if you look at a detail screen like <https://toolsadmin.wikimedia.org/tools/id/replag> and a Diffusion repo is no longer listed. We still have record of the Diffusion repos in the database. The GitLab replacement will show up as soon as it has been migrated.