Re: pagure pull-request email workflow

2020-07-24 Thread Richard W.M. Jones
On Wed, Jul 22, 2020 at 02:19:59PM +0200, Mark Wielaard wrote: > Hi Tom, > > On Tue, 2020-07-21 at 13:53 +0100, Tom Hughes via devel wrote: > > On 21/07/2020 13:12, Mark Wielaard wrote: > > > > I normally just edit .git/config and add to the origin remote > > > > an extra fetch: > > > > > > > > f

Re: pagure pull-request email workflow

2020-07-22 Thread Tom Hughes via devel
On 22/07/2020 15:59, Mark Wielaard wrote: That is not how I understand the current situation. CPE has a proposal to provide a forge for use by the fedora project possibly based on gitlab, but pagure wouldn't go away. I think you may be behind the times. The pretend consultation is over and th

Re: pagure pull-request email workflow

2020-07-22 Thread Mark Wielaard
Hi, On Wed, 2020-07-22 at 09:32 -0400, Neal Gompa wrote: > On Wed, Jul 22, 2020 at 9:19 AM Tom Hughes via devel > wrote: > > > > On 22/07/2020 13:19, Mark Wielaard wrote: > > > > > As you say, the web api is even more resourceful and we can integrate > > > some of those requests into the librar

Re: pagure pull-request email workflow

2020-07-22 Thread Neal Gompa
On Wed, Jul 22, 2020 at 9:19 AM Tom Hughes via devel wrote: > > On 22/07/2020 13:19, Mark Wielaard wrote: > > > As you say, the web api is even more resourceful and we can integrate > > some of those requests into the library: https://pagure.io/api/ > > > > The only thing that is not very nice are

Re: pagure pull-request email workflow

2020-07-22 Thread Tom Hughes via devel
On 22/07/2020 13:19, Mark Wielaard wrote: As you say, the web api is even more resourceful and we can integrate some of those requests into the library: https://pagure.io/api/ The only thing that is not very nice are those pagure_tokens. I was hoping you could get a temporary one through simple

Re: pagure pull-request email workflow

2020-07-22 Thread Mark Wielaard
Hi Tom, On Tue, 2020-07-21 at 13:53 +0100, Tom Hughes via devel wrote: > On 21/07/2020 13:12, Mark Wielaard wrote: > > > I normally just edit .git/config and add to the origin remote > > > an extra fetch: > > > > > > fetch = +refs/pull/*/head:refs/remotes/origin/pull/* > > > > > > then after fet

Re: pagure pull-request email workflow

2020-07-21 Thread Tristan Cacqueray
On Tue, Jul 21, 2020 at 12:25 Tom Hughes via devel wrote: > On 21/07/2020 11:56, Mark Wielaard wrote: > >> Do you have to handle them on that pagure website? Is it possible to >> handle these pull-request through email? Or is there a normal (git) >> command line interface for these? > > Pagure sup

Re: pagure pull-request email workflow

2020-07-21 Thread Tom Hughes via devel
On 21/07/2020 13:12, Mark Wielaard wrote: I normally just edit .git/config and add to the origin remote an extra fetch: fetch = +refs/pull/*/head:refs/remotes/origin/pull/* then after fetching you can merge origin/pull/NNN. But this is very helpful! Thanks. So with that I can easily do chec

Re: pagure pull-request email workflow

2020-07-21 Thread Mark Wielaard
On Tue, 2020-07-21 at 12:25 +0100, Tom Hughes via devel wrote: > On 21/07/2020 11:56, Mark Wielaard wrote: > > > Do you have to handle them on that pagure website? Is it possible > > to > > handle these pull-request through email? Or is there a normal (git) > > command line interface for these? >

Re: pagure pull-request email workflow

2020-07-21 Thread Tom Hughes via devel
On 21/07/2020 11:56, Mark Wielaard wrote: Do you have to handle them on that pagure website? Is it possible to handle these pull-request through email? Or is there a normal (git) command line interface for these? Pagure supports the same pull heads are things like github so yes you can just fe

pagure pull-request email workflow

2020-07-21 Thread Mark Wielaard
Hi, I got a pagure pull-request for my package (a first!). But I am slightly confused how to handle this. The email that pagure sents is not very helpful since it doesn't include the actual patch to try out. Also when I replied to the email it seems to have not gone to the actual submitter (and j