OK. Since there is no consensus. I'll keep doing so in my private repo and keep
the current scheme for public pushes.
Emmanuel
On 14 juil. 2011, at 10:07, Hardy Ferentschik wrote:
> +1 and I think this undueness applies not only to HHH ;-)
>
> On Wed, 13 Jul 2011 22:49:08 +0200, Steve Ebersole
2011/7/14 Hardy Ferentschik :
> +1 and I think this undueness applies not only to HHH ;-)
Quoting Emmanuel: "issues related to the project " [of the pull request]
So there should be no doubt.
> On Wed, 13 Jul 2011 22:49:08 +0200, Steve Ebersole
> wrote:
>
>> I guess maybe this is hassle based on
+1 and I think this undueness applies not only to HHH ;-)
On Wed, 13 Jul 2011 22:49:08 +0200, Steve Ebersole
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.
___
hibe
I guess maybe this is hassle based on which project key you are talking
about. For HHH- that is not an undue burden imo.
On Tue 12 Jul 2011 04:50:08 AM CDT, Sanne Grinovero wrote:
> +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
+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 firs
On 12 juil. 2011, at 10:49, Emmanuel Bernard wrote:
>>> 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
>> convi
On 12 juil. 2011, at 10:39, Hardy Ferentschik wrote:
>>
>> 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'
>
> See, what you are loosing here is the ability to cut&paste the branch
On Tue, 12 Jul 2011 10:30:21 +0200, Emmanuel Bernard
wrote:
> Today for pull requests, we do push to a branch named after the JIRA
> issue
> eg 'git push manu HSEARCH-123'
If on a feature branch I just do
git push my-fork HEAD
this way I don't have to type a branch name at all (well, obv
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 scop
