This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

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.

Release History

Release History

0.1.0

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.0.4

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.0.3

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
gitrisk-0.1.0.tar.gz (4.4 kB) Copy SHA256 Checksum SHA256 Source Jun 3, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting