| commit | 60924fdc2972184494f6382d39e8c786aa14b9a9 | [log] [tgz] |
|---|---|---|
| author | Xdng Yng <wyverald@gmail.com> | Wed Jul 31 01:46:57 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jul 31 01:48:23 2024 -0700 |
| tree | 9ee835ebadbe3c45666ead953f15a4f74b8d99b7 | |
| parent | dde97404d0c8c6fb04134b942993d94994a9c14e [diff] |
Use `+` instead of `~` as the canonical repo name separator This PR essentially flips `--incompatible_use_plus_in_repo_names` (introduced in https://github.com/bazelbuild/bazel/pull/23103) to true on master. In addition, it graveyards the flag, removes all logic to use `~`, and fixes all tests to use `+` instead. Closes #23098. RELNOTES: The format of canonical repo names has changed to use plus (`+`) instead of tilde (`~`). Effectively, this flips the flag `--incompatible_use_plus_in_repo_names` to true, and the flag is now a no-op (i.e. cannot be "unflipped"). PiperOrigin-RevId: 657913333 Change-Id: Ia97609049871db7a914fe3129556cf843d06f571
{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
