| commit | ec48fa6b3ba932e8ed4733890481b73c265223cc | [log] [tgz] |
|---|---|---|
| author | Christopher Sauer <cpsauer@users.noreply.github.com> | Tue Nov 22 20:00:29 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Nov 22 20:01:25 2022 -0800 |
| tree | 783ce042b23e0da57b1fa8aff29c8a9e61a400dc | |
| parent | b47ce12adc1abdb81ba524312577f0ed40940846 [diff] |
Improve list formatting in .bazelrc docs Hi wonderful Bazelers, I was reading the [.bazelrc docs](https://bazel.build/run/bazelrc) and noticed that a [list at the end was getting rendered as a single line](https://bazel.build/run/bazelrc#global-bazelrc), probably because GitHub's markdown rendering handles the need for newlines before lists differently than whatever Bazel uses to generate HTML from the docs. So, to try to leave things even better than I found them, I 1. Added a blank line above to try to fix that issue. 2. Since the list is intended to convey order, I changed it to an ordered (numbered) list. (Attempting to be maximally consistent with the other formatting in the doc: number, followed by two spaces, without blank lines in between for a short list.) Thanks for reading! Chris (ex-Googler) Closes #16814. PiperOrigin-RevId: 490395806 Change-Id: I917ff57cf857f6307dc5776d1f57f69dd566b514
{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
