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

Configure Scrutinizer CI #9

Merged
merged 2 commits into from
Mar 28, 2017
Merged

Configure Scrutinizer CI #9

merged 2 commits into from
Mar 28, 2017

Conversation

cemsbr
Copy link
Owner

@cemsbr cemsbr commented Mar 28, 2017

No description provided.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 85.222% when pulling b6c5e81 on scrutinizer into f7f0258 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 85.222% when pulling 23c4c80 on scrutinizer into f7f0258 on master.

@cemsbr cemsbr force-pushed the scrutinizer branch 2 times, most recently from 8f5e6d7 to e73a2f0 Compare March 28, 2017 18:32
@coveralls
Copy link

Coverage Status

Coverage remained the same at 85.222% when pulling e73a2f0 on scrutinizer into f7f0258 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 85.222% when pulling e73a2f0 on scrutinizer into f7f0258 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 85.222% when pulling f19c7ea on scrutinizer into f7f0258 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 85.222% when pulling c7e2d67 on scrutinizer into f7f0258 on master.

Changelog:
- Continuous Integration with:
  - Code quality score
  - Test coverage
@coveralls
Copy link

Coverage Status

Coverage remained the same at 85.222% when pulling cf0d04e on scrutinizer into f7f0258 on master.

@cemsbr cemsbr merged commit cf0d04e into master Mar 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants