Fix the documentation of `repository_rule(local = ...)` (#31823) ### Description Rewrites the `doc` of the `local` parameter of `repository_rule`. The old text said a local repo "should be reevaluated at every fetch". The new text says what Bazel actually does: - A local repo is refetched on the usual triggers (a change to the rule definition, its attributes, or a file it reads), plus after every Bazel server restart, because its contents are never reused from a previous server or from the repo contents cache (`shouldUseCachedRepoContents` in `RepositoryFetchFunction`). - It is not refetched on every build. - It is excluded from `bazel vendor` by default (`isRepoExcludedFromVendoringByDefault`). ### Motivation "Every fetch" reads as "every build", which is why #16217 was filed as a bug. The answer there was that this is working as intended and that local repo rules are additionally rerun at every server restart. This PR puts that explanation into the reference docs. Fixes #28497 ### Build API Changes No ### Checklist - [ ] I have added tests for the new use cases (if any). - [x] I have updated the documentation (if applicable). ### Release Notes RELNOTES: None Closes #31823 COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/31823 from cycancode:fix-repository-rule-local-doc dd56b854747e525bcdf63cf10f524d7a27ffbd04 PiperOrigin-RevId: 1008812672 Change-Id: Icb7775ab74292c19dbfa860cce93df01614b65ba
{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
