We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, Thanks for this action, it is very helpful !
It would be nice to have two distinct a new parameter which would be : minimum_coverage_per_file
Example:
- name: cobertura-report uses: 5monkeys/cobertura-action@v13 with: path: cobertura/coverage/cobertura.xml minimum_coverage: 75 minimum_coverage_per_file: 70
And result would be
75%
100%
50%
Minimum coverage requirement was not satisfied (75% global and 70% per file )
70%
- name: cobertura-report uses: 5monkeys/cobertura-action@v13 with: path: cobertura/coverage/cobertura.xml minimum_coverage: 85 minimum_coverage_per_file: 75
87%
Minimum coverage requirement satisfied (85% global and 75% per file )
85%
The text was updated successfully, but these errors were encountered:
In our project we currently can't fail a build when a single files is below the threshold. The suggested option would come in very handy here!
Sorry, something went wrong.
No branches or pull requests
Hi,
Thanks for this action, it is very helpful !
It would be nice to have two distinct a new parameter which would be : minimum_coverage_per_file
Example:
And result would be
first example KO
75%
75%
100%
100%
50%
50%
Minimum coverage requirement was not satisfied (
75%
global and70%
per file )second example OK
87%
87%
100%
100%
75%
75%
Minimum coverage requirement satisfied (
85%
global and75%
per file )The text was updated successfully, but these errors were encountered: