Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

document the patchbot #12505

Closed
dandrake opened this issue Feb 13, 2012 · 6 comments
Closed

document the patchbot #12505

dandrake opened this issue Feb 13, 2012 · 6 comments

Comments

@dandrake
Copy link
Contributor

At #12486, we add Robert Bradshaw's patchbot to Sage so that anyone can run a patchbot. We should document it, though!

*EDIT:

The code is now commented, at least a little.

And some doc on how to use it is available here:

https://wiki.sagemath.org/buildbot

CC: @robertwb @kini

Component: documentation

Keywords: patchbot

Reviewer: Kwankyu Lee

Issue created by migration from https://trac.sagemath.org/ticket/12505

@dandrake dandrake added this to the sage-5.11 milestone Feb 13, 2012
@jdemeyer jdemeyer modified the milestones: sage-5.11, sage-5.12 Aug 13, 2013
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.1, sage-6.2 Jan 30, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.2, sage-6.3 May 6, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@fchapoton

This comment has been minimized.

@fchapoton
Copy link
Contributor

Changed keywords from none to patchbot

@fchapoton fchapoton modified the milestones: sage-6.4, sage-6.8 Jul 12, 2015
@fchapoton

This comment has been minimized.

@mkoeppe mkoeppe removed this from the sage-6.8 milestone Dec 29, 2022
@mkoeppe
Copy link
Member

mkoeppe commented Jan 5, 2023

comment:9

outdated; the patchbot will be retired

@kwankyu
Copy link
Collaborator

kwankyu commented Jan 5, 2023

Reviewer: Kwankyu Lee

@kwankyu
Copy link
Collaborator

kwankyu commented Jan 5, 2023

comment:10

Yes.

@mkoeppe mkoeppe closed this as not planned Won't fix, can't repro, duplicate, stale Feb 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants