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

Create a Bot #14

Open
ForbesLindesay opened this issue Jan 9, 2013 · 3 comments
Open

Create a Bot #14

ForbesLindesay opened this issue Jan 9, 2013 · 3 comments

Comments

@ForbesLindesay
Copy link
Member

It would be really nice if this automatically got run against every known, compliant promises/A+ implementation every time it was updated so that:

a) authors wouldn't need to re-run tests even if they haven't changed anything
b) we'd know that authors weren't just telling people they were promises/A+ compliant without running this test suite.

@ForbesLindesay
Copy link
Member Author

It could be done as a travis build so we wouln't have to host any hardware to run it.

@domenic
Copy link
Member

domenic commented Jan 10, 2013

This is a great idea. The specifics might be tricky---e.g. if a library fixes itself, who's responsible for re-running the Travis build? I wonder if Travis has an API?

@ForbesLindesay
Copy link
Member Author

Travis does have an API, but I don't think it lets you re-build someone else's repo. If we gave all the implementers commit access to said repo then we could just let them add a new line with a comment to a 'history.md' file and cause it to build?

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

2 participants