(No Ticket): Added a debug mode to GitRisk so that debugging output can be seen.
Issue #9: Added a findSuspectCommits() function that will search for all commits within a given range.
Issue #9: Added basic skeleton for checkMerge() that will be used for checking whether a given merge has potential regressions, and added a command line parameter to execute this function from the command line.
Issue #9: Make GitRisk.findSuspectCommits() return a set instead of a list so that duplicate commits aren't reported, and add a test case for a more complicated use case of this function.
Issue #9: Added new function, getTicketsFromCommit(), that allows a user to retrieve tickets within a commit message.
Issue #9: Add a more complex test case to test_getTicketsFromCommit().
Issue #9: Added a test for when a commit message does not reference a ticket.
Issue #9: Refactored getTicketsFromCommit() to only return the first search result, and added tests to test edge cases in commit/ticket parsing.
Issue #9: Add function to retrieve a set of "suspect" commits reachable from the merge commit on which git-risk was run, but not reachable from the last common ancestor.
Issue #9: Add command line option to gitrisk that makes it minimally functional in detecting potential sources of regressions.
Issue #9: Add command line support for 'quiet mode', so that git-risk can be run from the command line and only output the results in terms of potential regression(s).
Issue #9: Refactor GitRisk object to include outputResults() so that everything is contained within a single object.
Issue #9: Refactor GitRisk object to encapsulate "quiet mode" inside of it as a setting, rather than passing it to the output function, for clarity.