| commit | 7af31ee557671ad8240c3b7a673a809c030b45da | [log] [tgz] |
|---|---|---|
| author | Greg Edelston <gredelston@google.com> | Tue Aug 23 16:24:47 2022 -0600 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 23 22:39:48 2022 +0000 |
| tree | e87b6b100df65108c8b0deec79ca5f42a4d13d0e | |
| parent | a01bae257112397f45c9a2aac545f508778cbadb [diff] |
GEConfig: Remove `optional` from rubik tgt mstone The `optional` label is disallowed in the proto 3 syntax, and infra/config outright refuses to work with it. Fields are optional by default, so the typical fix is to just remove the label. BUG=b:243532953 TEST=./generate.sh --allow-breaking Change-Id: I6597f3c5ef893657e4ec91c6ee154cbe93c3ab96 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3852629 Commit-Queue: Benjamin Shai <bshai@google.com> Reviewed-by: Benjamin Shai <bshai@google.com> Commit-Queue: Greg Edelston <gredelston@google.com> Auto-Submit: Greg Edelston <gredelston@google.com>
This repository exists in two locations in the tree: infra/proto, and chromite/infra/proto. The infra/proto repository is always at ToT, while the chromite/infra/proto checkout is branched to allow the proto there to (more) accurately reflect the version of the proto the Build API is using.
When making changes to the proto that you need to test in the Build API, you will need ensure the changes are applied to the chromite/infra/proto checkout. Chromite generates its proto bindings from the chromite/infra/proto repo.