commit | 63556dec09bde629d76f416eae2a1d04529a8a10 | [log] [tgz] |
---|---|---|
author | Blaze Rules Copybara <blaze-rules@google.com> | Tue Oct 18 06:36:44 2022 -0700 |
committer | Blaze Rules Copybara <blaze-rules@google.com> | Tue Oct 18 06:36:44 2022 -0700 |
tree | e6a7dede33c987612f7782358ae2c60b89241461 | |
parent | ba401432feeb79a4174a134f533aef4054331343 [diff] | |
parent | 0ec8c838b9dd5be1a00f4688226f58c6f6c7d324 [diff] |
Merge pull request #156 from comius:workspace-with-main PiperOrigin-RevId: 481905618
This repository contains Starlark implementation of Protobuf rules in Bazel.
For a high-level overview of using Protocol Buffers and gRPC with Bazel, see https://bazel-contrib.github.io/SIG-rules-authors/proto-grpc.html.
For the list of Proto rules, see the Bazel documentation.
To get started with rules_proto
, add the WORKSPACE
file snippet from the latest release.
Then, in your BUILD
files, import and use the rules:
load("@rules_proto//proto:defs.bzl", "proto_library") proto_library( ... )
If you're migrating from the native proto rules to rules_proto
, you can use the following buildifier command to automate the changes to your BUILD
and .bzl
files:
buildifier --lint=fix --warnings=native-proto <path/to/BUILD>
Bazel and rules_proto
are the work of many contributors. We appreciate your help!
To contribute, please read the contribution guidelines: CONTRIBUTING.md.
Note that the rules_proto
use the GitHub issue tracker for bug reports and feature requests only.
For asking questions see:
#proto
on slack.bazel.build