From be63dcc0049f157a52ea376e8259020afbe5891d Mon Sep 17 00:00:00 2001 From: Alexey Sergeev Date: Thu, 3 May 2012 22:41:18 +0300 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 13ceb40..73b93ee 100644 --- a/README.md +++ b/README.md @@ -30,7 +30,7 @@ Jira have to be available via http and be either publicly available otherwise yo In Jira bug ticket has type *Bug*, and feature ticket has type *New Feature*. Tool assumes that each commit message should look like: 
(ABC-123) This is my commit
-i.e. at the beginning of the message issue key defined in the round braces that is followed by commit comment. +i.e. at the beginning of the message issue key should be defined in the round braces that is followed by commit commentary. ##How it works### Initial idea was to analyse sources history within specified period of time (that's why I named tool *ranged-view*). But unfortunately hg4j library that I've used does not support such a feature yet. So tool analyses repository commits from the latest change set on out to the configured maximum number of commits back in history.