(Proudly) add a badge for the Scrutinizer code quality score #122
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. Add title tags to the badges on top of the page 2. Update year in the footer > 2016
eyecatchup
added a commit
that referenced
this pull request
Feb 6, 2016
(Proudly) add badge for Scrutinizer code quality score
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Today, I (finally) set up Scrutinizer for SEOstats and as soon as I activated the webservice hook, the tool started analyzing the SEOstats source code. And a few minutes later, I was suddenly presented with the Scrutinizer Code-Quality Rating-Score for SEOstats.
To my own surprise the resulting score turned out better than expected.
9.44 / 10 - Not bad, huh?! 🍻 😎
That really deserves (yet) another poser badge on the README, I thought. 😉 So, here we go: