git-risk is a command that will determine which tickets are at risk of regressions from a range of commits. It is most useful when used after a merge to determine which tickets were affected by the merge by searching through the range [<merge-commit>..<least common ancestor(merge-commit)>]. In this mode, it determines the least common ancestor of the commits included in the given merge and reports all tickets identified in the commit messages for all commits in between each of the merged commits and their least common ancestor.
The theory is that, for a given merge commit, regressions will typically be seen in tickets that weren’t previously merged into the main development trunk. Tickets that have already been merged into the main development trunk, and are tested prior to the merge in question, are at a lower risk for regressions. As such, git-risk provides a list of all tickets that haven’t yet been tested after the merge in question, so they can be tested to ensure lower probability of regressions in the happy-path of the code.
git-risk can also be used to report which tickets were involved (or, at least mentioned) within any range of commits.
For any of these to work, you must have a standard commit message format that includes the issue to which a given commit relates. Extraction of the ticket from a commit message is performed using a regular expression, so a great deal of flexibility is available.
Metadata
Release files for gitrisk 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gitrisk-0.1.0.tar.gz | 4.4 kB | Without provenance | Details for gitrisk-0.1.0.tar.gz |
Release files / gitrisk-0.1.0.tar.gz
| Download URL | gitrisk-0.1.0.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6336e1657cf5b1bead24cf61b14733134b66417868934416c87799d7aadacada
|
|
BLAKE2b-256 checksum How to use checksums |
a2dfa1a283f5cf2917e09b903f9bf28227a106c9bec77a3f52e6e82b792de388
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gitrisk 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.