<div dir="ltr"><div><div>Hi DM/all,<br><br>Just on branch naming, my personal experience is it's counter-productive to use a JIRA issue number as the branch name, because it has no intrinsic meaning.<br>At work we have a lot of people who use the issue number, and have to juggle between branches CR-12345, CR-72938, and CR-12453. The name doesn't give any intent: you have to look up the issue to find what it means.<br>
</div>Personally, I would much prefer to have branches like av11n and VerseKeyRefactor (no matter how arbitrarily named) that mean something to me. Usually they don't have to mean anything to anyone else.<br><br></div>
Having the issue number in the final commit does make a lot of sense.<br><div><br>Jon<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 17, 2014 at 12:52 AM, DM Smith <span dir="ltr"><<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">I like that idea for naming branches. I've been rather willy-nilly about them.<div>
<br></div><div>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?</div><div><span class="HOEnZb"><font color="#888888"><br>
<div>-- DM</div></font></span><div><div class="h5"><div><br><div><div>On Mar 16, 2014, at 9:34 AM, Greg Hellings <<a href="mailto:greg.hellings@gmail.com" target="_blank">greg.hellings@gmail.com</a>> wrote:</div><br>
<blockquote type="cite"><p dir="ltr">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.</p>
<p dir="ltr">--Greg</p>
<div class="gmail_quote">On Mar 16, 2014 8:25 AM, "DM Smith" <<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I've just updated the CrossWire tracker (Jira) to hook into Git on GitHub.<br>
<br>
We'll get better issue tracking if we do the following:<br>
Create issues and note the short name of the issue (E.g. JS-224)<br>
When committing in git, use the short name as the prefix of the commit message.<br>
(It actually doesn't have to be a prefix, but I don't know if the connector looks deep into the commit message.)<br>
<br>
Then in Jira you see the commit in the issue.<br>
<br>
In Him,<br>
DM<br>
<br>
<br>
<br>_______________________________________________<br>
jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org" target="_blank">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
<br></blockquote></div>
_______________________________________________<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org" target="_blank">jsword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
</blockquote></div><br></div></div></div></div></div><br>_______________________________________________<br>
jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
<br></blockquote></div><br></div>