Closed cordoval closed 10 years ago
Better next time do this through fork (the usual way) ignoring fact, that you have push access. This way Packagist won't index you PR branch as it did now.
it was all handled because we had permissions on github repo as you already noticed.
Then you added this repo under your Scrutinizer CI account?
yes, it is fine, once it is setup is publicly accessible
@cordoval, how you're able to get Scrutinizer CI integration working? I thought, that just having push access to the repo doesn't allow us to pretend to be GitHub's
hamcrest
user on Scrutinizer website to enable the integration.