| commit | e507ccded37c389186afaeb2b836ec576dc875dc | [log] [tgz] |
|---|---|---|
| author | Ignas Anikevicius <anikevicius@gmail.com> | Thu Jan 27 10:47:55 2022 +0200 |
| committer | GitHub <noreply@github.com> | Thu Jan 27 09:47:55 2022 +0100 |
| tree | d5dc9efd1ab627dd30c31986580cc7c9eaecf464 | |
| parent | 244e0b64fdc6a89df8b1750eada7b909b3cbc459 [diff] |
Update code annotations to 'starlark' (#105) Inspired by #47, we can use 'starlark' as annotations for the markdown files.
This repository contains Starlark implementation of Protobuf rules in Bazel.
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 = "66bfdf8782796239d3875d37e7de19b1d94301e8972b3cbd2446b332429b4df1", strip_prefix = "rules_proto-4.0.0", urls = [ "https://mirror.bazel.build/github.com/bazelbuild/rules_proto/archive/refs/tags/4.0.0.tar.gz", "https://github.com/bazelbuild/rules_proto/archive/refs/tags/4.0.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