| commit | 60934e289ce46b5e86f86176b9b1b4328cef7426 | [log] [tgz] |
|---|---|---|
| author | Sara Adams <sara@engflow.com> | Thu May 04 05:11:50 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu May 04 05:13:18 2023 -0700 |
| tree | 2fcb9a4681d04748d03abd1cea5c0f711003fb39 | |
| parent | 275c8bdbadb04bd7bf958fc360183fd7c13e2a06 [diff] |
[Documentation] Clarify `BUILD` file names The documentation currently refers to `BUILD` files with only a small side note that the may be called `BUILD.bazel`, namely where packages are defined. Instead, add a more prominent note to the page explaining `BUILD` files and clarify there that both namings are valid, that `BUILD.bazel` takes precendence, and that the documentation will talk just about `BUILD` files for simplicity's sake. Additionally, link to that page from the package definition section. Progress on https://github.com/bazelbuild/bazel/issues/4517 Closes #18251. PiperOrigin-RevId: 529378158 Change-Id: If74903e0a9ffd4410a9c65c1fc9f3e5959fe83a7
{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
