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

Support for Wercker #265

Closed
Potherca opened this issue Sep 8, 2014 · 3 comments
Closed

Support for Wercker #265

Potherca opened this issue Sep 8, 2014 · 3 comments

Comments

@Potherca
Copy link

Potherca commented Sep 8, 2014

Travis is nice, but personally I am enjoying the experience of Wercker more. Having support for the Wercker CI Server would be awesome!

As I have also opened issue #260, I was wondering if it might be wiser to try and add these services myself and add a PR. If so, what's the best way to get started on this?

@nicolindemann
Copy link
Contributor

Just do it.

@espadrine
Copy link
Member

That would definitely be great!

To get started, I recommend reading /INSTALL.md. Then, you can probably copy some code from, say, /server.js, around line 220, and modify it so that it reads data from Wercker CI (each system usually has its own API through a set of URLs). To be nice with future contributors, you should preferably add comments describing where the Wercker documentation is. Test your changes on localhost, either directly by adding a badge to /try.html, or by testing with a badge URL, /wercker/something/here.svg.

espadrine added a commit that referenced this issue Oct 26, 2014
@espadrine
Copy link
Member

This will be live in 48h.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants