| commit | 487796bbc21bdef3aedeb98435d274d3ec96ddc8 | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Sat Oct 26 19:31:18 2024 -0700 |
| committer | GitHub <noreply@github.com> | Sun Oct 27 02:31:18 2024 +0000 |
| tree | 65ee9e8a13e8269c53d95efc2690665d07a12c56 | |
| parent | 2f04951d055460947c461dc308a546ceb192f1a3 [diff] |
docs: tell how to create a release branch for patch releases (#2329) This adds some doc for how to create a branch when a patch release needs to be based on the original release and not from head. --------- Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com>
This repository is the home of the core Python rules -- py_library, py_binary, py_test, py_proto_library, and related symbols that provide the basis for Python support in Bazel. It also contains package installation rules for integrating with PyPI and other indices.
Documentation for rules_python is at https://rules-python.readthedocs.io and in the Bazel Build Encyclopedia.
Examples live in the examples directory.
The core rules are stable. Their implementation is subject to Bazel's backward compatibility policy. This repository aims to follow semantic versioning.
The Bazel community maintains this repository. Neither Google nor the Bazel team provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases. See How to contribute page for information on our development workflow.
For detailed documentation, see https://rules-python.readthedocs.io
See Bzlmod support for more details.