aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorGravatar Laszlo Csomor <laszlocsomor@google.com>2015-03-25 17:05:04 +0000
committerGravatar Damien Martin-Guillerez <dmarting@google.com>2015-03-25 20:04:58 +0000
commit7fad36a8fca28dc920598256922cd8ac0f7c04a5 (patch)
treeeefb64742feb80c04989031461df2f6c670e0c4a
parentda692516011da518e677de46aaa812fbcc4a9d4c (diff)
Bazel docs: fix broken link in Skylark's rules.md
-- MOS_MIGRATED_REVID=89511308
-rw-r--r--docs/skylark/rules.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/skylark/rules.md b/docs/skylark/rules.md
index 29278c62f9..c353eac5eb 100644
--- a/docs/skylark/rules.md
+++ b/docs/skylark/rules.md
@@ -72,7 +72,7 @@ Targets
Every build rule corresponds to exactly one target. A target can create
[actions](#actions), can have dependencies (which can be files or
-other build rules), [output files](#output_files) (generated by
+other build rules), [output files](#output-files) (generated by
its actions) and [providers](#providers).
A target `y` is depending on target `x` if `y` has a label or label list type
@@ -106,7 +106,7 @@ my_rule = rule(
)
```
-Output files
+Output files {#output-files}
------------
A target can declare output files, which must be generated by the target's
@@ -123,7 +123,7 @@ actions. There are three ways to create output files in Skylark:
[See example](cookbook.md#outputs-custom)
All output files must have exactly one generating action. See the
-[library](library.html#outputs) for more context.
+[library](library.html#modules.ctx.outputs) for more context.
Actions