Update badges to new job locations

[mmitche]

No description provided.

[mmitche]

The old pr test and commit jobs have now been disabled (though not deleted yet)

[ghost]

@mmitche, can we also get hook to codecov-io summary in PRs with this cool new groovy-driven infrastructure? :)

It will look something like:

• updated readme to point out canonical reference twitter-archive/diffy#8 (comment)
• One data detector instance per type TTTAttributedLabel/TTTAttributedLabel#581 (comment)
• SA1513 no longer reported for closing brace in first part of conditio… DotNetAnalyzers/StyleCopAnalyzers#1605 (comment)

(it will be just one comment per PR regardless of number of rebases / adding or removing commits; as they mentioned here: dotnet/corefx#3368)

[mmitche]

We don't today run code coverage on every PR, but I'll probably add it as an on-demand thing. I can look to add the hook then.

[mmitche]

Anyone have objections to me merging this?

[ghost]

@mmitche,
That sounds good. Probably @sharwell and co. can help us configuring code coverage and codecov hook, as they already have done it for several repos under https://github.com/DotNetAnalyzers.

Sorry I forgot to comment on the organization of badges earlier, but wouldn't it be nice to have it transposed such that Debug/Release become columns and platforms rows; essentially to get rid of the scroll bars with the ever growing matrix?
Also, in future the platform names may grow in length; "FreeBSD 10.2 x86 Release" or "Linux on ARM v7 (64-bit) Debug" etc.

[sharwell]

@jasonwilliams200OK codecov.io automatically detects when the build is running on AppVeyor and links the information to the parent repository, so there's no need to set up any hooks or authentication keys or anything. Our configuration to enable code coverage reporting is contained within the test_script section of our appveyor.yml, plus one line in our solution-level packages.config file. After setting everything up I contributed some (hopefully) helpful information back in codecov/example-csharp#3.