It's been a long-time coming, but we've added support for Checkstyle reports! Checkstyle is the JUnit of style reporting - except it's actually seemingly an official standard.
Checkstyle reports are a new feature, so we expect edge cases to crop up as it gets used accross various CI systems. As always, please let us knowif you run into trouble.
More forgiving authorization
Docs were a little ambigous on how to set your repo's token. Now, as long as you manage to get your repo's token somewhere in the auth header, it should be accepted. Now, all of the following should work:
curl --user token:YOUR_ID curl --user YOUR_ID: curl --user :YOUR_ID curl --user token:"token:YOUR_ID"
- swiftlint reported errors when it should have reported failures.
- typescript reported errors when it should have reported failures.
- eslint was parsed as swiftlint.
junit sometimes showed passing tests when it should have failed.
Previously, we had been relying on the root
testsuite's summary attributes to determine if the overall check run had passed or failed, but many reporters don't properly include those summary attributes. Now, we take the greater of a given summary value or a count of the number of
testcasenodes under that