Closed ilya-hontarau closed 1 month ago
Can you elaborate on what kind of change you are suggesting? Currently, if Go files were changed, this action will already show the impact on the unit test coverage of the repository.
I think it can be done in the way codecov does and golangci lint
Thanks for the suggestion, now I see what you mean.
To be honest, the scope of this GitHub action is to provide a high level summary of the changes with a single comment. What you are suggesting sounds interesting but is far beyond that scope. If you would like to have more elaborate features around code coverage, you are probably better of using codecov or another dedicated service for code coverage :sweat_smile:
Add warnings for code changes in pull requests that dont have test coverage.