On Thu, 2015-04-23 at 11:31 +0200, Tollef Fog Heen wrote: > ]] Ian Campbell > > > On Thu, 2015-04-23 at 08:12 +0200, Tollef Fog Heen wrote: > > > ]] Paul Wise > > > > > > > Also accept contributions via email or git request-pull. > > > > > > How do I set up a service to accept git request-pull pull requests into > > > a workflow? There does not seem to be any protocol associated with it, > > > so «accept contributions via git request-pull» seems underspecified. > > > > All "git request-pull" does is output an email template, including a url > > +branch and a summary of the changes (subjects, authors, diffstat) found > > at that location relative to a baseline (which is also specified). > > So there is no way to accept contributions via git request-pull. There > is no transport protocol, unless you say «email», in which case it's > just «please accept contributions via email».
Right, except it is waay more convenient for the receiver than the other email based options (patch bombs and such) > > The layout is consistent so it's not unimaginable to create some service > > or script could consume such a mail, pull the changes and register them > > into whatever you want. > > Sure, just like you could hook email machinery into github's pull > request model where you have a bot on a mailing list that manages the > pull requests on the user's behalf. Probably, I've no idea, I was just responding to the question about how git request-pull was used. Ian. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1429783955.12403.1.ca...@hellion.org.uk
