commit | 7f3d2b0f33f02f23d27827f91824e483a35b53b6 | [log] [tgz] |
---|---|---|
author | Otabek Kasimov <otabek@google.com> | Thu Jul 11 22:17:29 2024 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 11 22:42:14 2024 |
tree | a04bd17f879bbc1756c661e663bb65217a7913b9 | |
parent | b3fdd32718bf343e6a815663e506185c0ccf5c29 [diff] |
protos: add new version structure fro new versions BUG=b:352455603 TEST=run regenerate.sh Change-Id: I5745fc1c01710fb359c643f3816de14d18214c9e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/5698013 Reviewed-by: Chris DeLaGarza <cdelagarza@google.com> Commit-Queue: Otabek Kasimov <otabek@google.com> Auto-Submit: Otabek Kasimov <otabek@google.com>
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.