Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / infra / proto / refs/heads/stabilize-15054.115.B
commita129aac4875cecd72343e9da724a467133c4414b[log] [tgz]
authorGeorge Engelbrecht <engeg@google.com>Mon Aug 15 18:01:48 2022 -0600
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Aug 16 01:03:35 2022 +0000
tree308686782c3332965b8cd01f62b2016e49e9a281
parente7ae691cea4b94494808e1c3bfe642522186941a [diff]
common.proto: removed rubik channel enum

BUG=None
TEST=./generate.sh

Change-Id: I58420d1a7644243462af951b1c423d6e6c0865cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3832209
Commit-Queue: Benjamin Shai <bshai@google.com>
Reviewed-by: Benjamin Shai <bshai@google.com>
Auto-Submit: George Engelbrecht <engeg@google.com>
3 files changed
tree: 308686782c3332965b8cd01f62b2016e49e9a281
  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.