Ned Batchelder
Ned Batchelder
You already have this feature today. Instead of adding an option to pytest-cov, you simply have to add one line to your GitHub action workflow.
@marcosboger I'm not a maintainer here so it's not my decision. And as I mentioned in my comment, I'm generally not in favor of jamming more features into this tool...
I guess I'm really missing something. Why invent strange ways to append from within the pytest command-line? There's already a command you can run that generates the markdown, and you...
I can see that is very complex indeed. I can't puzzle through all of it. Is there a reason you can't use `coverage report --format=markdown` and append the output to...
#623 may be related.
Thanks for the detailed write-up! It sounds convincing. I will work through the reproduction soon.
There are some subtle details to figure out if we are going to make this change. - Should the new "files are relative to the location of .coveragerc" rule be...
Just to clarify: this issue in particular is about the mention of the coverage data file, not the Python files that are being executed. There are four kinds of files...
An idea from @fschulze (https://twitter.com/fschulze/status/1354423765225115648): coverage could define an environment variable with the directory configuration was read from. Then you could use that variable in your .coveragerc file. Actually, come...
> > Actually, come to think of it: you can define that environment variable yourself. Would that work for you? The simpler we can keep coverage.py, the better :) >...