Mirroring of www-gitlab-com is broken
Problem
Mirroring of https://gitlab.com/gitlab-com/www-gitlab-com is broken. The mirroring is set up as a Pull
mirror on the security repo and has not successfully ran since 2023-02-28: https://gitlab.com/gitlab-org/security/www-gitlab-com/-/settings/repository
The dev mirror has no mirroring set up and has not updated since November 2022: https://dev.gitlab.org/gitlab/www-gitlab-com/-/settings/repository
Exit Criteria
-
Update canonical repository based on the security content. - This will require a push to
master
. We might want to give a heads-up on the #handbook slack channel for this. - If we don't want to push to master, we should open up a merge request on canonical with the content of security, and use the merge-train for merging. This would be the preferable option.
- This will require a push to
-
Setup a mirroring from canonical to security https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/security/mirrors.md -
Setup a mirroring from security to dev https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/security/mirrors.md - This might not be necessary if we don't have the handbook repo on dev.
-
Ensure no one can merge into the master
branch of the Security repository This should prevent accidental merges in the security repo. #19742 (comment 1641696630)
Possible impact
At first glance, the security mirror does not seem to be used for anything other than the preparation of the security release blog posts. With the way we currently move blog posts from security to canonical, having the mirror so far behind could cause errors or delays in the creation of the canonical MR.
Since the dev mirror does not seem to be used at all currently. There are 3 issues that are 7+ years old, and the only MRs merged there were done so at least 3 years ago.