James Kessler

# Closing this PR without accepting its changes **Thank you @mike-burns and @Thompson1985 for your contributions and for starting this discussion!** After reviewing this proposal to treat all method definitions...

Thanks, @dgw. We will have another look at this. The question is: Why were previous conditional statement (with branch coverage) showing partial coverage (yellow) when their child branches had misses...

@iurev @nebolsin thanks! I have shared the solution with the customer. I Cc'd Vitalii on the email thread so he can confirm I gave the right info, and be included...

Closing this PR. Added the [changes](https://github.com/coverallsapp/coverage-reporter/pull/103/files) directly to the latest README, here: https://github.com/coverallsapp/coverage-reporter?tab=readme-ov-file#troubleshooting 🙏

Thank you, @kjstouffer! We aim to review and merge this week after a new planned release.

@kjstouffer we have been working on that same release and have faced some challenges. Therefore, I'm reviewing right now and will merge and cut a new release as soon as...

Checks passed and changes have been [merged](https://github.com/coverallsapp/coverage-reporter/commit/f8732dd3cd635756dacb38dd482e1244fefaac0e). Give me 30 min or so to cut the new release. I need to revert some CI/CD changes related to the other release...

OK @kjstouffer, changes pushed to new release `0.6.14`: https://github.com/coverallsapp/coverage-reporter/releases

Hi @csiefer2. Yes, this can happen with large C/C++ projects. [coverage-reporter](https://github.com/coverallsapp/coverage-reporter), which underlies our [github-action](https://github.com/coverallsapp/github-action), can process however many coverage report files you have in your environment, but above a...

@csiefer2 We did not hear back on this, so closing it in hopes that it's resolved. If not, please re-open or test again with the latest version of `coverage-reporter` (`v0.6.15`)...