Would you support an option to fail the action if coverage is below X?

[nambrosini17]

It would be useful to take action based on coverage

[ewjoachim]

Yes I think you're right that it would make sense, especially since this action may do the merge operation. That said, if you have only a single coverage file or if you merge the files yourself, you can use coverage or pytest-cov to do it.

[nambrosini17]

Interesting, hadn't thought of that. I'll try it and report back. Thanks for creating such a useful too and for this alternative too

[nambrosini17]

I've tried but coverage and pytest lack the options of establish the check only on modified code. Since it's a large codebase i want to enforce the threshold only on modified code (say 90%) when the overall coverage is way below that number.
The reasoning would be to elevate the bar for new code, without being forced to tackle missing coverage of unmodified code.
Since the tool already does the "coverage over modified files" logic, i wonder if it would be easier to support it that way vs adding another dependency to my ci that needs configuration.

Let me know what you think and if you're interested in me exploring a PR