Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / infra / proto / refs/heads/stabilize-15208.B
commit47b184ae2064283ff969dfb6c25ac3b35c27b4e1[log] [tgz]
authorMadeleine Hardt <hardtmad@google.com>Fri Oct 21 22:43:56 2022 +0000
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Oct 21 22:57:23 2022 +0000
tree1893589327c34ae18c87b7634b9b171df9eb75ac
parentdede3558f7d5a0acd4dc47fa0960c27157b13bf8 [diff]
ge_config: Remove optional which is not allowed in proto 3

oops, this broken regen in infra/config.

BUG=b:247155374
TEST=./generate.sh

Change-Id: I92043a3faa542e2603f57600c0f61c2216b77931
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3970786
Reviewed-by: George Engelbrecht <engeg@google.com>
Reviewed-by: Jack Neus <jackneus@google.com>
Commit-Queue: Madeleine Hardt <hardtmad@google.com>
3 files changed
tree: 1893589327c34ae18c87b7634b9b171df9eb75ac
  1. extern/
  2. gen/
  3. go/
  4. infra/
  5. recipes/
  6. src/
  7. .gitattributes
  8. .gitignore
  9. buf.yaml
  10. generate.sh
  11. LICENSE
  12. OWNERS
  13. PRESUBMIT.cfg
  14. PRESUBMIT.py
  15. README.md
  16. setup_cipd.sh
  17. unblocked_terms.txt
README.md

infra/proto

infra/proto vs chromite/infra/proto

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.