Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / infra / proto / refs/heads/main
commitb50ce0dcbae8cf7c7748e1a25e12c15436ac94db[log] [tgz]
authorAndrew Lamb <andrewlamb@chromium.org>Thu Oct 05 20:55:56 2023 +0000
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Oct 06 21:24:52 2023 +0000
treeac9809888ffcdcd6d2839393140abdc95e7adb4f
parent01c02f054114388ea9f44d6ae38a01d2472a50f7 [diff]
Remove specific OWNERS for src/device.

- Repo-level owners are fine for this dir.

BUG=None
TEST=None

Change-Id: I1538a69ec1a529699179c0b6bfafc0dd7f08264e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/4916221
Reviewed-by: Jack Neus <jackneus@google.com>
Reviewed-by: George Engelbrecht <engeg@google.com>
Commit-Queue: Andrew Lamb <andrewlamb@chromium.org>
1 file changed
tree: ac9809888ffcdcd6d2839393140abdc95e7adb4f
  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.