aboutsummaryrefslogtreecommitdiffhomepage
path: root/site
diff options
context:
space:
mode:
authorGravatar laurentlb <laurentlb@google.com>2018-07-20 05:22:07 -0700
committerGravatar Copybara-Service <copybara-piper@google.com>2018-07-20 05:23:34 -0700
commitcb7ed1693f4da77c85f0873adbac522deb9ea60f (patch)
treec380eb6af8f35e31ce5026bc6f73f516771ab93d /site
parenta0043e5277a6fcb8f2a01264d827dc6f5425fe85 (diff)
Rules are no longer experimental.
Exact API will continue to evolve, some specific functions are experimental, but we can't really say that the concept of rule is experimental. RELNOTES: None. PiperOrigin-RevId: 205383939
Diffstat (limited to 'site')
-rw-r--r--site/docs/skylark/rules.md3
1 files changed, 0 insertions, 3 deletions
diff --git a/site/docs/skylark/rules.md b/site/docs/skylark/rules.md
index 85a1941e25..ad550cd745 100644
--- a/site/docs/skylark/rules.md
+++ b/site/docs/skylark/rules.md
@@ -5,9 +5,6 @@ title: Rules
# Rules
-**Status: Experimental**. We may make breaking changes to the API, but we will
- announce them.
-
A rule defines a series of [actions](#actions) that Bazel should perform on
inputs to get a set of outputs. For example, a C++ binary rule might take a set
of `.cpp` files (the inputs), run `g++` on them (the action), and return an