commit | 70b42485395e0fa376f32b9e7f4012a70d6121d2 | [log] [tgz] |
---|---|---|
author | Blaze Rules Copybara <blaze-rules@google.com> | Tue Oct 18 07:30:30 2022 -0700 |
committer | Blaze Rules Copybara <blaze-rules@google.com> | Tue Oct 18 07:30:30 2022 -0700 |
tree | 52be10651c5e7d354b961bf8b908b1698b6dea4a | |
parent | 63556dec09bde629d76f416eae2a1d04529a8a10 [diff] | |
parent | 87d5c27667b0b613d5f6471faef973a90c72e166 [diff] |
Merge pull request #154 from neumann-nico:protobuf-21.7 PiperOrigin-RevId: 481915517
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