Re: Git workflow

On 2015-01-12, Nicolas Lalevée wrote: > I’m not sure though why some of my commits didn’t get to do it: > https://github.com/apache/ant-ivy/commit/3f9eb02b76c31665b6ff44b11d4017f08065f4f3 > > github isn't tracki

Re: Git workflow

On 2015-01-12, Nicolas Lalevée wrote: > I’m not sure though why some of my commits didn’t get to do it: > https://github.com/apache/ant-ivy/commit/3f9eb02b76c31665b6ff44b11d4017f08065f4f3 > > No idea either, sor

Re: Git workflow

> Le 11 janv. 2015 à 18:46, Stefan Bodewig a écrit : > > On 2015-01-11, Nicolas Lalevée wrote: > >> By the way, is there any way to close manually the pull requests in >> github ? The only way is to reference it in a git commit ? > > Probably some infra folks can since you need write access to

Re: Git workflow

On 2015-01-11, Nicolas Lalevée wrote: > By the way, is there any way to close manually the pull requests in > github ? The only way is to reference it in a git commit ? Probably some infra folks can since you need write access to the github apache organization. You can create empty commits (--al

Re: Git workflow

By the way, is there any way to close manually the pull requests in github ? The only way is to reference it in a git commit ? Nicolas > Le 11 janv. 2015 à 13:17, Nicolas Lalevée a > écrit : > > >> Le 7 janv. 2015 à 05:57, Stefan Bodewig a écrit : >> >> On 2015-01-07, Nicolas Lalevée wrote

Re: Git workflow

> Le 7 janv. 2015 à 05:57, Stefan Bodewig a écrit : > > On 2015-01-07, Nicolas Lalevée wrote: > >> For instance, to get commits from one branch to the other, I have seen >> two ways: via merge or via cherry-pick. >> Since our branches are meant to diverge à some point, I think using >> cherry-p

Re: Git workflow

On 2015-01-07, Nicolas Lalevée wrote: > For instance, to get commits from one branch to the other, I have seen > two ways: via merge or via cherry-pick. > Since our branches are meant to diverge à some point, I think using > cherry-pick should be used, right ? Alternatively develop the feature on