2 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: CreatingSubRepository.md
Insertions: 2, Deletions: 0.
@@ -20,6 +20,7 @@
- Add "google-go-team" team with Write access.
- Add "robots" team with Write access (can only be done by a maintainer of golang organization; ask someone else if you're not).
3. Modify the [`x/build/repos`](https://golang.org/x/build/repos) package.
+ - Also modify the [`x/build/devapp/owners`](https://dev.golang.org/owners) to include the owner(s) of the new repository. (Both can be updated in one CL.)
4. Modify the [`PROJECTS` map](https://cs.opensource.google/go/x/build/+/luci-config:main.star;l=644-675;drc=67d27da0c4496ee84405c96517dfdaaf4e960cfc) on [luci-config](https://cs.opensource.google/go/x/build/+/luci-config:README) branch.
5. Update x/website's version of x/build to include modified `x/build/repos` package.
- `x/website/cmd/golangorg` will [deploy automatically](https://go.googlesource.com/website#deploying) on CL submission.
@@ -28,4 +29,5 @@
2. `x/build/maintner/maintnerd`
- Note that it's expected for the new repo not to appear in maintner until first issue or PR is created (see [#25744](https://go.dev/issue/25744)).
3. `x/build/cmd/gerritbot`
+ 4. `x/build/devapp`
6. You're done.
```
CreatingSubRepository: update for migration to LUCI
Include a few changes that are relevant now that LUCI is used for
testing. Notably, the luci-config branch needs to be updated, and
it's fine not to redeploy coordinator. Clarify that the x/website
deployments are automatic, and add a reminder to add repo owner(s).
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |