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 sitting in that image unless it's been redone since then). I don't remember if I ever pushed anything back to github (which would require write access) but pull requests should get closed when their associated changes get merged into master.
On Mon, Jul 18, 2016 at 2:00 PM, Paul Masson <paulmas...@comcast.net> wrote: > Samuel, there are a couple pull requests from the middle of 2015 that never > became Trac tickets. The bot appears to have stopped creating tickets before > then. > > There are open pull requests from the end of 2014 that became part of Sage > 6.4. The bot does not appear to close pull requests on GitHub. > > The infrastructure wiki page lists Volker and Harald as the only admins for > GitHub. Are there any others who could close the ten or so open items ready > for closure in the Sage repository? If not, perhaps I'll bug Harald about > it. > > This may of course seem trivial to people, but if Sage is planning to move > to GitHub in the future then then it makes sense to begin addressing GitHub > maintenance more actively. > > > > On Monday, July 18, 2016 at 1:12:31 AM UTC-7, 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 new public release of Sage happens (github >> pull >> requests are typically against the master branch and public releases are >> when >> this branch gets updated). >> >> The bot is maintained by Robert Bradshaw, he might be able to comment >> more. >> See https://wiki.sagemath.org/Infrastructure >> >> >> Le dimanche 17 juillet 2016 23:06:37 UTC+2, Paul Masson a écrit : >>> >>> Thanks. >>> >>> Another question: who closes Issues and Pull Requests on Github that have >>> been marked ready for closure? >>> >>> On Sunday, July 17, 2016 at 1:56:38 AM UTC-7, Volker Braun wrote: >>>> >>>> done >>>> >>>> On Saturday, July 16, 2016 at 11:19:21 PM UTC+2, Paul Masson wrote: >>>>> >>>>> The mirror actually has three branches. This one hasn't been touched in >>>>> over a year: >>>>> >>>>> https://github.com/sagemath/sage/tree/module-list-cleanup >>>>> >>>>> Shouldn't it be removed at some point? >>>>> >>>>> On Wednesday, July 13, 2016 at 6:53:21 PM UTC-7, John Phamlore wrote: >>>>>> >>>>>> The mirror at >>>>>> >>>>>> https://github.com/sagemath/sage >>>>>> >>>>>> has only two branches, develop and master. Versions seem to be kept >>>>>> as tags. >>>>>> >>>>>> However, editing sage.yaml of binary-pkg >>>>>> >>>>>> https://github.com/sagemath/binary-pkg >>>>>> >>>>>> does not work for tags. > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
