Bazel Docs: Remove all DevSite tags from new .mdx docs. GCLI created a Python script in unknown commit that did all the heavy lifting. This is a breaking change, but unfortunately Mintlify isn't going to support custom heading IDs in the near future. Workarounds are being tracked in https://github.com/bazel-contrib/bazel-docs/issues/252 Our best course of action is to fix the parsing errors by removing the custom IDs, then proceed with the workarounds. PiperOrigin-RevId: 879883162 Change-Id: I328765485bf3dacf4118357083488abb796ba2bc
{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
