Misha Kav
I find the solution in a similar package https://github.com/marketplace/actions/jest-coverage-comment
@kir0ul can you try please this: ```bash issues: write pull-requests: write ``` [more info](https://github.blog/changelog/2021-04-20-github-actions-control-permissions-for-github_token/#setting-permissions-in-the-workflow)
Looks like you do a `fork` you don't have permission to run the action. Looks like it GitHub issue as described https://github.com/actions/first-interaction/issues/10#issuecomment-562178406
Found a solution to generate collapsed report at this action [Jest Coverage Comment](https://github.com/marketplace/actions/jest-coverage-comment)
Found a solution to work with multiple files at this action [Jest Coverage Comment](https://github.com/marketplace/actions/jest-coverage-comment#:~:text=Example%20GitHub%20Action%20workflow%20that%20uses%20multiple%20files%20mode%20(can%20be%20useful%20on%20mono%2Drepo%20projects))
I find the solution in a similar package https://github.com/marketplace/actions/jest-coverage-comment
Good idea, I will check the possibility to add this feature when got some time.
I checked the ability and even tried to add this feature. For now, it's tough, because it is written in pure javascript without any tests, so I scary to break...
Have the same issue. Found solution on similar GitHub Action: [Pytest Coverage Comment](https://github.com/marketplace/actions/pytest-coverage-comment) It uses `tee` in every example :)
Also may be solved with `workflow_run` like in this example #153