Google Git
Sign in
chromium / chromiumos / infra / proto / refs/heads/main
commit700b45dff50dfbad35dfb8d6d972c27dc95349d2[log] [tgz]
authorJon Murphy <jpmurphy@google.com>Thu Apr 17 18:28:18 2025
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Apr 18 22:43:45 2025
tree3b5ec5718d1ca1e1fab4d14abd151c0459d68871
parent14aaf771b41bf01498e83e4156e08cb3e5b7edcb [diff]
qual: Move types inside message

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

Change-Id: I80df349a934479cb0719407f2acae8bb4c6a2dbf
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/6470585
Reviewed-by: Jeremy Bettis <jbettis@chromium.org>
Commit-Queue: Jon Murphy <jpmurphy@google.com>
Reviewed-by: Cindy Lin <xcl@google.com>
3 files changed
tree: 3b5ec5718d1ca1e1fab4d14abd151c0459d68871
  1. bin/
  2. extern/
  3. gen/
  4. go/
  5. infra/
  6. recipes/
  7. src/
  8. .gitattributes
  9. .gitignore
  10. buf.yaml
  11. generate.sh
  12. LICENSE
  13. OWNERS
  14. OWNERS.tse
  15. PRESUBMIT.cfg
  16. PRESUBMIT.py
  17. README.md
  18. setup_cipd.sh
  19. 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.