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).

Change-Id: Idc49c555cc527c23aa348bc42597064c78e52d25
Reviewed-on: https://go-review.googlesource.com/c/wiki/+/596595
Auto-Submit: Dmitri Shuralyov <[email protected]>
Reviewed-by: Than McIntosh <[email protected]>

CreatingSubRepository.md

@@ -6,6 +6,7 @@ This page outlines the steps that need to be done to create a new golang.org/x r
 - a golang.org/x redirect
 - automatic git mirroring from Gerrit to GitHub
 - automatic importing of GitHub PRs into Gerrit CLs
+- automatic testing on appropriate Go builders
 
 ## Steps
 
@@ -18,13 +19,15 @@ This page outlines the steps that need to be done to create a new golang.org/x r
 		- Add "golang org admins" team with Admin access.
 		- 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` package.
-4. Update x/website's version of x/build to include modified `x/build/repos` package.
-5. Redeploy all affected commands (or ask an x/build [owner](https://dev.golang.org/owners) to deploy if you're not; the order shouldn't matter):
+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.
+6. Redeploy all affected commands (or ask an x/build [owner](https://dev.golang.org/owners) to deploy if you're not; the order shouldn't matter):
 	1. `x/build/cmd/gitmirror`
 	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/cmd/coordinator` 
-	5. `x/website/cmd/golangorg`
+	4. `x/build/devapp`
 6. You're done.