| Dmitri Shuralyov | 0ac9a27 | 2018-10-04 16:11:58 -0400 | [diff] [blame] | 1 | This page outlines the steps that need to be done after a new subrepository is added to go.googlesource.com, in order for it to get mirrored to GitHub, set up PR to Gerrit importing, etc.: |
| 2 | |
| 3 | - Create a new empty repository at https://github.com/golang with the same name, complete with a description. |
| 4 | - Turn off Wikis, Issues in repository settings. |
| 5 | - On "Collaborators & teams" tab: |
| 6 | - Add "golang org admins" team with Admin access. |
| 7 | - Add "gophers" team with Write access. |
| 8 | - Add "robots" team with Write access (can only be done by a maintainer of golang organization; ask someone else if you're not). |
| 9 | - Create "cla: yes" and "cla: no" labels, they need to exist so that [@googlebot](https://github.com/googlebot) can automatically apply them. (Without a "cla: yes" label, PRs won't be imported into Gerrit.) |
| 10 | - Modify 3 x/build commands: |
| 11 | - In `cmd/gerritbot`, add the new repo to `gerritProjectWhitelist` map. |
| 12 | - In `cmd/gitmirror`, add the new repo to `shouldMirror` function. |
| 13 | - In `maintner/maintnerd`, add the new repo to `goGitHubProjects` slice. |
| 14 | - See [an example commit](https://github.com/golang/build/commit/a196f5a8e8d347b6b9fe4cd225a3393a77c03214). |
| 15 | - Redeploy all 3: `cmd/gitmirror` first, `maintner/maintnerd` second, `cmd/gerritbot` third. |
| 16 | - Note that it's expected for the new repo not to appear in maintner until first issue or PR is created (see [#25744](https://golang.org/issue/25744)). |
