Today for pull requests, we do push to a branch named after the JIRA issue eg 'git push manu HSEARCH-123'

I propose that for issues related to the project (99.9% of the time), we instead use the numeric part of the issue as a branch name eg 'git push manu 123'

As Git repos are naturally scoped to the issues, that should not be a problem and it will help type less and help git-complete auto completion.

>> As Git repos are naturally scoped to the issues, that should not be a problem and it will help type less and help git-complete auto completion. > > How does this help git-complete? One less tab? I am not convinced. I am not convinced and > personally I like the full issue key. It just feels more right. One less tab and the fact that typing the number is as fast as typing tab pretty much.

+1. Often we mix many issue numbers in a pull request - as far as I see we're all fine in picking one of them as most significant, let me know if somebody strongly prefers 1:1 pull requests and issues.. that's more time consuming as it means we can't start working on depending issues until the first one is approved. The jboss.org JIRA has an automated process to automatically mark issues as fixed when the relevant pull request is merged in master. For this to work when issuing the pull request you still have to add a link to the pull request on a field in JIRA, so you still have to switch contexts, I'm not sure yet if we're winning some time. A definite improvement would be a "search provider" plugin for firefox, so that 1) I can paste issue numbers in the search box without opening JIRA first 2) As the Skype plugin does with telephone numbers converting them in "call this number links, have a plugin scanning the HTML of any service and email to convert them in JIRA links. This would be reasonable only if we keep the project part of the issue name too, but I guess we'll still have that in many other places (apart of the branch name). Something to try creating when all issues are solved :) Cheers, Sanne _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

+1 and I think this undueness applies not only to HHH ;-)

On Wed, 13 Jul 2011 22:49:08 +0200, Steve Ebersole <steve(a)hibernate.org&gt; wrote: > I guess maybe this is hassle based on which project key you are talking > about.  For HHH- that is not an undue burden imo.