From ecc11f9a4c06400d4797e7132e71fe8702490cf0 Mon Sep 17 00:00:00 2001 From: Geoffrey Martin-Noble Date: Wed, 12 Jan 2022 08:28:43 -0800 Subject: [PATCH] Fix name arg documentation for native_binary (#338) --- docs/native_binary_doc.md | 2 +- rules/native_binary.bzl | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/native_binary_doc.md b/docs/native_binary_doc.md index cb69179..1a330ca 100755 --- a/docs/native_binary_doc.md +++ b/docs/native_binary_doc.md @@ -26,7 +26,7 @@ You can "bazel run" this rule like any other binary rule, and use it as a tool i | Name | Description | Default Value | | :------------- | :------------- | :------------- | -| name | The name of the test rule. | none | +| name | The name of the rule. | none | | src | label; path of the pre-built executable | none | | out | output; an output name for the copy of the binary. (Bazel requires that this rule make a copy of 'src'.) | none | | data | list of labels; data dependencies | None | diff --git a/rules/native_binary.bzl b/rules/native_binary.bzl index 6675a92..9a1725f 100644 --- a/rules/native_binary.bzl +++ b/rules/native_binary.bzl @@ -72,7 +72,7 @@ def native_binary(name, src, out, data = None, **kwargs): You can "bazel run" this rule like any other binary rule, and use it as a tool in genrule.tools for example. You can also augment the binary with runfiles. Args: - name: The name of the test rule. + name: The name of the rule. src: label; path of the pre-built executable out: output; an output name for the copy of the binary. (Bazel requires that this rule make a copy of 'src'.) data: list of labels; data dependencies