Alexandre Conrad-Dormoy

Hi, thanks for raising this. Do the `` tags provide any relevant line coverage information? If we ignore them, would we miss anything? I don't have much time to make...

Can you provide a sample coverage file that is causing this issue?

> OK~ Here is a sample coverage file from a rust library, generated by https://github.com/mozilla/grcov https://github.com/CurryPseudo/rust-coverage/blob/main/cobertura.xml Thanks for sharing a coverage file. As far as I can tell, the lines...

Hmm, never heard about this use case before. What is the reasoning/workflow behind having your coverage report include files that aren't checked in? My assumption is that if the file...

Thanks @blueyed for the explanation. I definitely think we should have a nicer error message instead of a stack trace which is not user-friendly. As for the ignore/skip I have...

Hm. I think that's a good idea. We should still prevent missing files from crashing pycobertura to address the root issue. But ignoring coverage for files included in .gitignore could...

New lines seem like a useful metric to display. I can see how people can get a sense of how large the change is by looking at "New". What about...

Works for me! If you want to add this to the output of pycobertura, go for it! 👍 I think it could be a useful metric to have by default.

Note: we currently support Markdown output in the latest master (which will be released with 3.0). The other features I see here are: * regex matching to control the files...

It's hard for me to tell without a working test case. But I am confused about what you are confused about. ;) First you say: > 2nd row shows +60%...