Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / infra / proto / 0a3ac5ffeeec2bfd6a130d9082aa4ab5c5ca7fef
commit0a3ac5ffeeec2bfd6a130d9082aa4ab5c5ca7fef[log] [tgz]
authorEli <elijahtrexler@google.com>Wed Oct 04 14:13:37 2023 +0000
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Oct 04 18:24:31 2023 +0000
treea8f229d17b82c1c53b30fed89be015accd102d0b
parent27169a6f25d10f2b025ece9646d0234de5cf9723 [diff]
sfp: Change value->values in repeated field

Acknowledge this is a breaking change, but this is not used anywhere
yet.

Test Plan=review generated

Change-Id: I4ef513098ab458d038514da8d1717d7f4e17c1ca
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/4911853
Reviewed-by: Jack Neus <jackneus@google.com>
Commit-Queue: Eli Trexler <elijahtrexler@google.com>
3 files changed
tree: a8f229d17b82c1c53b30fed89be015accd102d0b
  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.