Change Details

We have plenty of repositories which can use a renaming (T125031 and there are others). With the Zuul upgrade, we will have support to trigger a job based on regex based upon the repository name. Thus for example we could have a job for `^mediawiki/libs/.*` repositories. I also found that repositories inherited access lists from `All-Projects.git` and went to replicate some of the access lists given from what should have been their parent (eg `operations`, `mediawiki`) which is a bit cumbersome. From T239693#9516209: > > From T201953, I have finally added to our Gerrit instance the [[ https://gerrit.wikimedia.org/r/plugins/rename-project/Documentation/index.html | rename-project plugin ]] which provides a [[ https://gerrit.wikimedia.org/r/plugins/rename-project/Documentation/cmd-rename.md | rename-project ssh command ]] (as well as a REST API entry point). There are several things to check [ ] Rename the repository in the GitHub mirror [ ] Verify whether the repo is renamed on the replicas [ ] If relevant update the URL in packagist.org [ ] Update codesearch? Stretch: maybe we can keep a list of repositories that got renamed and use that to generate web/git redirects from the old repo to the new one. I don't think it is worth the hassle though.

We have plenty of repositories which can use a renaming (T125031 and there are others). With the Zuul upgrade, we will have support to trigger a job based on regex based upon the repository name. Thus for example we could have a job for `^mediawiki/libs/.*` repositories. I also found that repositories inherited access lists from `All-Projects.git` and went to replicate some of the access lists given from what should have been their parent (eg `operations`, `mediawiki`) which is a bit cumbersome. From T239693#9516209: > > From T201953, I have finally added to our Gerrit instance the [[ https://gerrit.wikimedia.org/r/plugins/rename-project/Documentation/index.html | rename-project plugin ]] which provides a [[ https://gerrit.wikimedia.org/r/plugins/rename-project/Documentation/cmd-rename.md | rename-project ssh command ]] (as well as a REST API entry point). There are several things to check [ ] Rename the repository in the GitHub mirror [ ] Verify whether the repo is renamed on the replicas (it is not: T398401) [ ] If relevant update the URL in packagist.org [ ] Update codesearch? Stretch: maybe we can keep a list of repositories that got renamed and use that to generate web/git redirects from the old repo to the new one. I don't think it is worth the hassle though.

We have plenty of repositories which can use a renaming (T125031 and there are others). With the Zuul upgrade, we will have support to trigger a job based on regex based upon the repository name. Thus for example we could have a job for `^mediawiki/libs/.*` repositories. I also found that repositories inherited access lists from `All-Projects.git` and went to replicate some of the access lists given from what should have been their parent (eg `operations`, `mediawiki`) which is a bit cumbersome. From T239693#9516209: > > From T201953, I have finally added to our Gerrit instance the [[ https://gerrit.wikimedia.org/r/plugins/rename-project/Documentation/index.html | rename-project plugin ]] which provides a [[ https://gerrit.wikimedia.org/r/plugins/rename-project/Documentation/cmd-rename.md | rename-project ssh command ]] (as well as a REST API entry point). There are several things to check [ ] Rename the repository in the GitHub mirror [ ] Verify whether the repo is renamed on the replicas (it is not: T398401) [ ] If relevant update the URL in packagist.org [ ] Update codesearch? Stretch: maybe we can keep a list of repositories that got renamed and use that to generate web/git redirects from the old repo to the new one. I don't think it is worth the hassle though.