| commit | 2918ef9be6016580a527eb25892e083c374d667b | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <richardlev@gmail.com> | Tue Sep 02 17:03:34 2025 -0700 |
| committer | Richard Levasseur <rlevasseur@google.com> | Wed Sep 03 10:37:06 2025 -0700 |
| tree | a32857ba2ae4ca0758bf99fa211d64a46a577d2f | |
| parent | 24146a49cc34269d1dd7f7cd334fa80e0c8a2935 [diff] |
chore: allow release workflow to be manually run and skip pypi upload (#3232) This makes it possible to manually invoke the release workflow and skip the pypi upload. This is useful if the release workflow was cancelled (or failed) after the pypi upload step. Work towards https://github.com/bazel-contrib/rules_python/issues/3188 (cherry picked from commit 6610fd742ae804cf2d8374b98d5fc4a9d949d9bb)
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.