irongut

I tried using this Action with permissions `issues: write` and it failed. (I'm assuming that's what the bot means above)

@protoblade Afaik all GitHub hosted runners use x86_64, I assume you're using a self hosted runner for this? I'll give it some thought over the weekend.

The problem is CCS uses a cached image created at release to speed up workflows that use it. The cached image is built on an x86 runner so the image...

## coverage.py Sample ```xml ``` (Details not relevant to CCS omitted.)

Hi @pboling thanks for the sample, that's always useful. Looking at the sample there are no branch metrics on coverage or package nodes. Unfortunately the `hide_branch_rate` option only hides it...

@pboling Looking at the docs, enable branch coverage but leave primary coverage set to the default of line. That should be compatible with the current version of CCS. I'll add...

Hi @ardalis, at the moment CCS doesn't produce a badge for the readme but it is a feature I'd like to have. Ideally CCS would download the badge from shields.io...

That is an interesting solution. If I incorporate uploading the json file into CCS then the user would need to create a gist and supply its id and a PAT...

@tlevesque-ueat Is this reading a single coverage file or two coverage files? If it's a single file then those values come from the coverage file with no additional maths on...

Hi @grofit I've not seen that done before. Could you tell me what task you're using to get those results?