On Fri, Jul 01, 2016 at 11:25:40AM -0700, Stefan Beller wrote:
> > So a litmus test for me would be something like:
> >
> > Can you get the same effect with:
> >
> > git push $remote my-branch &&
> > curl https://$remote/api/do-the-thing?q=my-branch
> >
> > as you would with:
> >
> >
On Fri, Jul 1, 2016 at 10:55 AM, Jeff King wrote:
> On Fri, Jul 01, 2016 at 10:07:10AM -0700, Stefan Beller wrote:
>
>> > So you'd probably want some client tool to help the user figure out what
>> > to put in the PR, and of course that already exists, because GitHub has
>> > an HTTP API that it c
On Fri, Jul 01, 2016 at 10:07:10AM -0700, Stefan Beller wrote:
> > So you'd probably want some client tool to help the user figure out what
> > to put in the PR, and of course that already exists, because GitHub has
> > an HTTP API that it can talk to. Shoe-horning it into Git doesn't buy
> > much
On Fri, Jul 1, 2016 at 12:09 AM, Jeff King wrote:
> On Wed, Jun 29, 2016 at 05:59:47PM -0700, Stefan Beller wrote:
>
>> Allow a user to pass information along a push to the pre/post-receive hook
>> on the remote.
>
> Seems like a reasonable thing to want, and related to:
>
> http://thread.gmane.
On Wed, Jun 29, 2016 at 05:59:47PM -0700, Stefan Beller wrote:
> Allow a user to pass information along a push to the pre/post-receive hook
> on the remote.
Seems like a reasonable thing to want, and related to:
http://thread.gmane.org/gmane.comp.version-control.git/285124
which was specifica
Allow a user to pass information along a push to the pre/post-receive hook
on the remote.
When using a remote that is more than just a plain Git host (e.g. Gerrit,
Git{hub/lab}, etc) this may become more obvious: The (server backend specific)
push options can instruct the server to:
* open a pull
6 matches
Mail list logo
