| commit | 14d1e26c8cec8722e60ab8b8ae32b10e42f732f9 | [log] [tgz] |
|---|---|---|
| author | kotlaja <kotlaja.nevena@gmail.com> | Mon Sep 19 15:45:34 2022 +0200 |
| committer | GitHub <noreply@github.com> | Mon Sep 19 15:45:34 2022 +0200 |
| tree | e3953754ed2829644da51a5a35ad8e0df8eef430 | |
| parent | 02cb6c29c5d677214c0b755890f7dd4472a51b3f [diff] |
Update BUILD Test automatic import to Piper.
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 following to your WORKSPACE file:
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") http_archive( name = "rules_proto", sha256 = "e017528fd1c91c5a33f15493e3a398181a9e821a804eb7ff5acdd1d2d6c2b18d", strip_prefix = "rules_proto-4.0.0-3.20.0", urls = [ "https://github.com/bazelbuild/rules_proto/archive/refs/tags/4.0.0-3.20.0.tar.gz", ], ) load("@rules_proto//proto:repositories.bzl", "rules_proto_dependencies", "rules_proto_toolchains") rules_proto_dependencies() rules_proto_toolchains()
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