| commit | 95ec95b3825fb6d612656501b702144d2fe668dd | [log] [tgz] |
|---|---|---|
| author | Googler <brandjon@google.com> | Fri Oct 21 14:33:43 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Oct 21 14:35:03 2022 -0700 |
| tree | 65a7faeb29174fcdc43cb162eeef5961a044807d | |
| parent | 9d98d7fd65b71bd58fa95c03f8d764d9a6c7b666 [diff] |
Rewrite visibility.md This is a major restructuring of the content in visibility.md. - Make two main headings: target visibility and bzl visibility. The latter remains a stub, to be filled in by a different CL. - Eliminate the best practices section, moving those bullet points inline into the relevant sections (called out as "Best practices:"). - Move more discussion/concepts to the top, before we get into visibility specifications. - Move obscure detail about package_group into its own stub section. While tiny, this parallels the distinction between rule targets, file targets, and package groups as the three main kinds of targets. - Turn warning about a cyclic dep error a formatted "Note:" callout. - Moved config setting into its own section, since it's a legacy edge case and not really relevant to rule targets in general. - Rephrased the sections on source file targets, config settings, and implicit deps, in an attempt to be clearer and more direct. I'm not in love with the examples on this page, but didn't attempt to touch them in this CL. The diff's already big enough for sure. Work toward #11261. PiperOrigin-RevId: 482890214 Change-Id: I5b0c7454228ff457319aeed04465af982132106b
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
