Closed aik099 closed 9 years ago
closed via fe0aca1cdb3905a05dd8efb7947fc332f57a298b
Can you please also send coverage information to Scrutinizer, so it would affect code quality score?
Here is the instructions: https://scrutinizer-ci.com/docs/tools/external-code-coverage/
reopening this due to last note
@cordoval , was this done?
I should do this, can you give me friday or do you want to go ahead and do this?
can you give me friday
You mean you'll have time to do this on friday? Sure, no hurry.
so it is configured https://coveralls.io/r/hamcrest/hamcrest-php the thing that we are missing is the https://scrutinizer-ci.com/docs/tools/external-code-coverage/ on it now
Ah, so the Coveralls.Io integration was there, but we're not posting Coverage Report back to Scrutinizer CI. I see.
That's quite easy to configure but requires changes from both Scrutinizer CI side (to enable external code coverage) and repo side (Travis CI config to send that coverage).
The actual coverage is already being collected for Coveralls.Io.
i have sent scrutinizer support message to see why this is not working cc @schmittjoh
badge is green now https://scrutinizer-ci.com/g/hamcrest/hamcrest-php/?branch=master
It seems, that former https://github.com/cordoval/hamcrest-php had integration with Coveralls.Io service (presence of it's config indicates that).
How about to enable that integration for this repo as well (and remove old one) with adding corresponding badges to README.md?