James Kessler

Hi @thoni56. Can you please share what version of `coverage-reporter` returned this error? I'm under the impression this was fixed in the latest release (`v0.6.12`), but if not, I would...

@mkungla Thanks for reporting this. I agree. I have asked for a review and bump in priority. I'll update you here with any changes.

Hi @erazemk, Yes! The feature is called [Carryforward Flags](https://docs.coveralls.io/parallel-builds#carryforward-flags), and you enable it by passing the `carryforward` flag with your call to the ([close](https://docs.coveralls.io/api-parallel-build-webhook)) [Parallel Build Webhook](https://docs.coveralls.io/api-parallel-build-webhook). (Here's a [little...

hi @marvinhagemeister Thank you for reporting your issue. We have identified it as being related to the incident we are currently working on here: https://status.coveralls.io/ You can subscribe to updates...

@marvinhagemeister et. al., **Status**: Wanted to let you know that we are in maintenance mode this morning (US PST timezone): https://status.coveralls.io/ Apologies for the inconvenience. Please track progress at the...

Hi @marthijn. What's happening is that you are uploading all three files at once. In that scenario, Coveralls will merge all the coverage reports in your upload, which in some...

Hi, @marthijn. You're welcome! > Because a dotnet build or dotnet test command will be executed on any target framework found in the solution (my strategy only includes .net 8.0.x),...

Hi @ricardoboss @marthijn @ricardoboss to answer your question: > So, my question for @afinetooth: are there plans to support URLs as filenames so we can have permalinks to the exact...

Yes, there is something strange going on there: Using your most recent build as the example: https://coveralls.io/builds/71568567 I noticed that, in **TREE view**, `OpenGraphBuilderFactory.cs` coverage is shown as `0%`: But...

Sounds good. FYI, the place to start might be in your Coveralls GitHub Action configuration settings. Specifically, if you believe the file paths in your original coverage reports are correct---meaning...