fix: replace HTML flag headers with markdown to prevent emdash rendering (https://github.com/bazelbuild/bazel/pull/29325) ## Summary - Flag names like `--verbose` on the [flag cheatsheet](https://preview.bazel.build/reference/flag-cheatsheet) are rendered with an emdash (—) instead of double dashes (`--`) due to Mintlify's smart typography converting `--` in prose contexts - Replaced `<h3><code><a>` HTML wrappers with markdown inline code links (`` [`--flag`](url) ``) for all 27 flags in `docs/reference/flag-cheatsheet.mdx` - Hyperlinks to the command-line reference are preserved - Mintlify preview: https://bazel-pr-29325.mintlify.app/reference/flag-cheatsheet Fixes bazel-contrib/bazel-docs#366 ## Test plan - [ ] Verify on Mintlify preview that flag names render with `--` (not —) - [ ] Verify flag names are still clickable links to the command-line reference 🤖 Generated with [Claude Code](https://claude.com/claude-code) Closes #29325. PiperOrigin-RevId: 906201733 Change-Id: I2b98f1ce504d7138e39034e8df0337bd34eb82f2
{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
