| commit | c36f7d4ae2463997bd1fcdf9386aa62b56ca8e8d | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <ci.bazel@gmail.com> | Wed Aug 14 12:55:46 2024 -0400 |
| committer | GitHub <noreply@github.com> | Wed Aug 14 12:55:46 2024 -0400 |
| tree | 99bfbba402255c9ffe298e6eb85510838618053e | |
| parent | 1acfc5f88683bbad49ba6f8622db66baf8bcf394 [diff] |
[7.3.1] Add a version indicator and selector to all docs pages (#23304) The header of each docs page now indicates the current version in bold and contains links to the same page for each other release with versioned docs. The template language usage in this change is based on publicly available information: https://github.com/GoogleCloudPlatform/DataflowTemplates/blob/97f69c065e9a049f43a5676b633d181ed0ac8448/plugins/core-plugin/src/main/resources/site-template.md?plain=1 <img width="1281" alt="Screenshot 2024-06-13 at 12 29 57" src="https://github.com/bazelbuild/bazel/assets/4312191/64deebcc-2d0e-4a16-9490-eacae2e12561"> Closes #22725. PiperOrigin-RevId: 644354576 Change-Id: I7c4e9208a79430d3c56c94674b70296a2a778a5f Commit https://github.com/bazelbuild/bazel/commit/2562707390fed314e2fb56eb6f92afa964117d25 Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
{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
