Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

2016-07-20 Thread William Stein
On Tue, Jul 19, 2016 at 10:08 PM, Robert Bradshaw wrote: > I was running a small script on trac.sagemath.org:12000 that was > listening for github pull requests and comments (via github webhooks) > and publishing them to trac (via the trac scripts shipped with Sage).

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

2016-07-19 Thread Robert Bradshaw
I was running a small script on trac.sagemath.org:12000 that was listening for github pull requests and comments (via github webhooks) and publishing them to trac (via the trac scripts shipped with Sage). Nothing too fancy, but I can't find the code for it at the moment (but it's probably still

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

2016-07-18 Thread Erik Bray
On Mon, Jul 18, 2016 at 12:46 PM, Thierry wrote: > Hi, > > On Mon, Jul 18, 2016 at 12:17:48PM +0200, Erik Bray wrote: > [...] >> Additionally, I think we should allow issues (without code) to be >> posted on GitHub, and have an easy way to convert a GitHub issue

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

2016-07-18 Thread Thierry
Hi, On Mon, Jul 18, 2016 at 12:17:48PM +0200, Erik Bray wrote: [...] > Additionally, I think we should allow issues (without code) to be > posted on GitHub, and have an easy way to convert a GitHub issue to a > Trac ticket. I don't think it should be done for all issues, but > rather use GitHub

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

2016-07-18 Thread Erik Bray
On Mon, Jul 18, 2016 at 10:12 AM, Samuel Lelievre wrote: > There is a bot (called sageb0t) that turns pull requests on GitHub into trac > tickets. > > It might be that the bot also closes pull requests when the corresponding > tickets > have been closed on trac and a