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.

Sign up for GitHub

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

Jump to bottom

Implement a CI in order to get build stats like code coverage etc. #33

Closed
maraisr opened this issue Feb 6, 2017 · 2 comments
Closed

Implement a CI in order to get build stats like code coverage etc. #33

maraisr opened this issue Feb 6, 2017 · 2 comments
Labels
discussion

Comments

@maraisr
Copy link
Contributor

maraisr commented Feb 6, 2017

Thinking if we use CircleCI along with Codecov and get our branches built through to we can safely say that any PR will pass our linting rules #32 and our tests #31, plus we'd be able to put a nice snazzy shields.io shield to show off our 100% code coverage report (once we get to it).

high-five
@jorgebucaran
Copy link
Owner

@maraisr Yes, CircleCI or Travis or both are fine! We need tests first though.

@jorgebucaran
Copy link
Owner

We have tests running on travis and coverage too. All thanks to @maraisr for introducing this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jorgebucaran @maraisr