code-coverage-action
code-coverage-action copied to clipboard
barecheck
GitHub Action that generates code coverage reports
Hey! I'm having trouble getting the extension setup: When I cat the lcov.info file generated, I get the following format: `lcov.info` ```ruby SF:./app/xxxxxx/xxxxx/xxxxxxxxxx.rb DA:1,0 DA:2,0 DA:3,0 DA:5,0 DA:6,0 DA:7,0 DA:8,0...
Currently, we don consider only files that were changed to make to show annotations only in changed lines. It would be good also, use lines that were changed to avoid...
src/lcov.js responsible to build grouped array of lines that are not covered but it's broken once we have empty lines. Would be great if we avoit this and have the...
https://github.com/actions/toolkit/pull/855 We already have annotations support but would be great to use official library to generate them. Recently, annotations were fixed in https://github.com/barecheck/code-coverage-action/pull/97
The idea is to have Github status check with coverage percentage along with comment that we already have ## Implementation As an example we can use this article https://www.infoq.com/news/2018/05/github-checks-api/ and...
Now, we are using the title to find what comment we should update. Would be great to move with filtering by author and use an application filter there also.
``` UnhandledPromiseRejectionWarning: HttpError: Resource not accessible by integration at /home/runner/work/code-coverage-action/code-coverage-action/dist/index.js:3441:23 at processTicksAndRejections (internal/process/task_queues.js:93:5) at async createComment (/home/runner/work/code-coverage-action/code-coverage-action/dist/index.js:6221:15) at async sendSummaryComment (/home/runner/work/code-coverage-action/code-coverage-action/dist/index.js:6050:5) at async runFeatures (/home/runner/work/code-coverage-action/code-coverage-action/dist/index.js:6671:3) at async runCodeCoverage (/home/runner/work/code-coverage-action/code-coverage-action/dist/index.js:6692:3) at...
Hi @melnychukvitaliy, thanks for this action! I think it is closest of the many like this to supporting my team's use case. The only friction for us is that we...
The gh action is failing with the following error: [Error: read ETIMEDOUT]. This seems to be related to a timeout issue occurring when attempting to send the test coverage summary...
