Bazel Docs: Add missing generated files to 9.0 release docs. https://github.com/bazelbuild/bazel/commit/6e1e226ec7d194d42f518f6add96f6a770e60c45 built the initial 9.0 docs, but missed all generated docs under rules/lib/repo because the html2mdx tool ignored all .md files. Since then we've upgraded html2mdx to docs2mdx, so I could cherry-pick those additional commits to recreated the 9.0 docs: <details> <summary>Commands</summary> ``` git checkout release-9.0.0 # remove file that should be generated, but was checked in by mistake: rm docs/reference/command-line-reference.mdx # revert 9.1.0 change: git revert 87aad180893bcd21cf049e64d3101cd3c7ef1981 git cherry-pick bc436e3e6c0240f604c2713ee23037b246813412 \ a4e5d848c35f63e827fc257e5ffb8722e06412ad \ 8ca49ef4554aa1f9d480dfcf18ebde63bd6f9995 \ 4c6b39b378cdc065515e2d9b63417b33772bd4c5 \ 8f80aeada1117968f5b76445811758c29367f1df \ 1c114e332fd5de02bad84ebab6796c627c2a8c1f \ e602c70edfbf1f4e779393851e5318989234b654 bazel build \ --config=docs \ //scripts/docs:gen_mdx_release_docs ``` </details> PiperOrigin-RevId: 895876591
{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.
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
