[jsword-devel] Jira and Git

[DM Smith]

I like that idea for naming branches. I've been rather willy-nilly about them.

Since it looks deep into the message, will it catch when a single commit solves multiple issues, provided that each issue is named in the commit message?

-- DM

On Mar 16, 2014, at 9:34 AM, Greg Hellings <greg.hellings at gmail.com> wrote:

> We use that hook and git-JIRA connection at work. The system will look deep into the messages for the short name. We force branches to also be named after the issue short name as well as including it in commit messages, thus allowing the plug in to find merges related to the issue as well.
> 
> --Greg
> 
> On Mar 16, 2014 8:25 AM, "DM Smith" <dmsmith at crosswire.org> wrote:
> I've just updated the CrossWire tracker (Jira) to hook into Git on GitHub.
> 
> We'll get better issue tracking if we do the following:
> Create issues and note the short name of the issue (E.g. JS-224)
> When committing in git, use the short name as the prefix of the commit message.
> (It actually doesn't have to be a prefix, but I don't know if the connector looks deep into the commit message.)
> 
> Then in Jira you see the commit in the issue.
> 
> In Him,
>         DM
> 
> 
> 
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel
> 
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/jsword-devel/attachments/20140316/638ec911/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4145 bytes
Desc: not available
URL: <http://www.crosswire.org/pipermail/jsword-devel/attachments/20140316/638ec911/attachment.p7s>