Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / infra / proto / refs/heads/stabilize-15245.B
commit6351bcf7a4cf8f1cd388290b7c108f039071c561[log] [tgz]
authorJustin Suen <justinsuen@google.com>Tue Nov 15 00:02:20 2022 +0000
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Nov 15 19:17:18 2022 +0000
treef61d63c6d97576953a0cf51a832bc641ed4cde41
parent3e1c12966d8af0efc3b065d306a39695604bdc70 [diff]
lab: fix typos in servo proto

BUG=NONE
TEST=./generate.sh

Change-Id: Ida747334f2b93a90fe555f968add8ce3db845cc5
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/4027225
Reviewed-by: Vineet Joshi <vkjoshi@google.com>
Commit-Queue: Justin Suen <justinsuen@google.com>
Reviewed-by: Otabek Kasimov <otabek@google.com>
Reviewed-by: Xixuan Wu <xixuan@google.com>
2 files changed
tree: f61d63c6d97576953a0cf51a832bc641ed4cde41
  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.