From the release you wish to use:
https://github.com/bookingcom/rules_pitest/releases
copy the WORKSPACE snippet into your WORKSPACE file.
To use a commit rather than a release, you can point at any SHA of the repo.
For example to use commit abc123:
url = "https://github.com/bookingcom/rules_pitest/releases/download/v0.1.0/rules_pitest-v0.1.0.tar.gz" with a GitHub-provided source archive like url = "https://github.com/bookingcom/rules_pitest/archive/abc123.tar.gz"strip_prefix = "rules_pitest-0.1.0" with strip_prefix = "rules_pitest-abc123"sha256. The easiest way to do this is to comment out the line, then Bazel will
print a message with the correct value. Note that GitHub source archives don't have a strong
guarantee on the sha256 stability, see
https://github.blog/2023-02-21-update-on-the-future-stability-of-source-code-archives-and-hashes/Check e2e/smoke/sample-from-upstream for an usage example
Once you do a bazel test you will find the reports in the compressed target bazel-testlogs/<path>/test.outputs/outputs.zip
0.0.2.bcr.1 +6h2025-04-16 | |
0.0.22025-04-16 |