You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(internal/postprocessor): be selective about what PRs to update (#7280)
This limits the scope of which PRs are updated by our postprocessor.
In the future we may actually want our post processor to run some
tidy commands and vet peoples code for them. But we should discuss
this with the rest of the team first.
Follow instructions in [OwlBot Usage Guide - "How will I test my .github/.OwlBot.yaml file"](https://g3doc.corp.google.com/company/teams/cloud-client-libraries/team/automation/docs/owlbot-usage-guide.md?cl=head#how-will-i-test-my-githubowlbotyaml-file) using the instructions for **split repositories**.
5
-
- Note, if you replace step 2 with a clone of your own fork of the `googleapis/googleapis-gen.git` repo, you can see how changes in your forked `googleapis-gen` repo are eventually propagated through to the library without making changes to the protos. Lack of permissions may also force you to clone a fork instead of the repo.
6
4
7
-
After following these steps the generated code will have replaced corresponding files in the `google-cloud-go` repo.
5
+
Follow instructions in [OwlBot Usage Guide - "How will I test my .github/.OwlBot.yaml file"](https://g3doc.corp.google.com/company/teams/cloud-client-libraries/team/automation/docs/owlbot-usage-guide.md?cl=head#how-will-i-test-my-githubowlbotyaml-file) using the instructions for
6
+
**split repositories**.
7
+
**Note**, if you replace step 2 with a clone of your own fork of the
8
+
`googleapis/googleapis-gen.git` repo, you can see how changes in your forked
9
+
`googleapis-gen` repo are eventually propagated through to the library without
10
+
making changes to the protos. Lack of permissions may also force you to clone a
11
+
fork instead of the repo.
12
+
13
+
After following these steps the generated code will have replaced corresponding
14
+
files in the `google-cloud-go` repo.
8
15
9
16
## Docker container
10
-
The Docker container needs to be built with the context of the entire `google-cloud-go/internal` directory. When building the container, do so from the `google-cloud-go/internal` directory
17
+
18
+
The Docker container needs to be built with the context of the entire
19
+
`google-cloud-go/internal` directory. When building the container, do so from
20
+
the `google-cloud-go/internal` directory
11
21
12
22
## Running the post-processor locally
13
-
The Docker container name needed will be found in the `.github/OwlBot.yaml` and `github/OwlBot.lock.yaml` files.
You can run the post-processor locally on selected directories or on all of the clients in the root directory.
34
+
35
+
You can run the post-processor locally on selected directories or on all of the
36
+
clients in the root directory.
23
37
24
38
### Run post-processor on all clients
25
-
From the `google-cloud-go/internal/postprocessor` directory run:
26
-
```sh
39
+
40
+
From the `google-cloud-go/internal/postprocessor` directory run:
41
+
42
+
```bash
27
43
go run main.go -stage-dir="../../owl-bot-staging/src/" -client-root="../.." -googleapis-dir="/path/to/local/googleapis"
28
44
```
45
+
29
46
### Run post-processor on select clients
30
-
From the `google-cloud-go/internal/postprocessor` directory run the same command, but with an added `dirs` flag containing a comma-separated list of the names of the clients on which to run the post-processor. The example below shows the commandfor running the post-processor on the `accessapproval` and `asset` libraries:
31
-
```sh
47
+
48
+
From the `google-cloud-go/internal/postprocessor` directory run the same
49
+
command, but with an added `dirs` flag containing a comma-separated list of the
50
+
names of the clients on which to run the post-processor. The example below shows
51
+
the command for running the post-processor on the `accessapproval` and `asset`
52
+
libraries:
53
+
54
+
```bash
32
55
go run main.go -stage-dir="../../owl-bot-staging/src/" -client-root="../.." -googleapis-dir="/path/to/local/googleapis" -dirs="accessapproval,asset"
0 commit comments