Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / infra / proto / refs/heads/firmware-ti50-mp-15224.B
commita082eb2305f35fba38c0869d74e58322c3786a7d[log] [tgz]
authorJack Neus <jackneus@google.com>Thu Sep 01 16:28:47 2022 +0000
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Sep 01 16:40:47 2022 +0000
tree9bf617e8009ff3e98450e25b4626dc0884b32c64
parent5eb9bc28804c35358d454d4dc71f36e4ec24040e [diff]
Add lts fields to FetchMilestoneScheduleResponse

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

Change-Id: I5228fece86db97264f3241ab7b520244becaf860
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3868325
Owners-Override: Jack Neus <jackneus@google.com>
Auto-Submit: Jack Neus <jackneus@google.com>
Commit-Queue: George Engelbrecht <engeg@google.com>
Commit-Queue: Jack Neus <jackneus@google.com>
Reviewed-by: George Engelbrecht <engeg@google.com>
3 files changed
tree: 9bf617e8009ff3e98450e25b4626dc0884b32c64
  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.