Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / infra / proto / refs/heads/firmware-chameleon-14947.B
commit3d5283458a3c0bdb07a8c7bb9692ad7d74a5d627[log] [tgz]
authorBob Haarman <inglorion@chromium.org>Fri Feb 04 01:08:31 2022 +0000
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jun 30 00:04:33 2022 +0000
tree739b176586a0be204a87ce72631693ebeb80e616
parenta15b289212b351be64a89c5de45e403ab5d5e5e5 [diff]
Add CreateBinhostCLs rpc and messages

BUG=b:196886631
TEST=generate.sh

Change-Id: Ia1690e702bddc29074b24c394ded52e969a88fd3
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3437624
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Sloan Johnson <sloanjohnson@google.com>
Commit-Queue: Bob Haarman <inglorion@chromium.org>
4 files changed
tree: 739b176586a0be204a87ce72631693ebeb80e616
  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.