Joachim Jablon

Hey Sam! I just realized I forgot to watch this repo. Sorry for the 2 year lag... I'll review your PR :)

I just realized I forgot to watch this repo. Sorry for the 2 year lag... The only usecase that has been extensively tested yet is to upload packages to PyPI...

I just realized I forgot to watch this repo. Sorry for the 2 year lag... So... Yeah. I use this project via [twine](https://twine.readthedocs.io/en/latest/), which was my main usecase. I'll welcome...

Yes we could do that. I believe that shields.io is supposed to handle this kind of load, but I understand your usecase.

Just a note: we'll still need to store some info in the wiki, not just the file, because this is used to know the evolution of coverage rate, which is...

So I've made [python-coverage-comment-action](https://github.com/ewjoachim/python-coverage-comment-action) and I'm not sure I want to spend a lot of time maintaining this action too. If you're interested in taking over, let me know :)

I didn't move this functionality in particular. What happened is that: - I needed to redo a huge part of the action in order to support external PRs that need...

Nooo sorry I wasn't clear :( The other action **doesn't have** this feature either.

So this is solved in https://github.com/ewjoachim/python-coverage-comment-action. I'm not sure I'm willing to spend a lot of time fixing it here.

I like this idea, this would allow a clear PR where you can check the diff, and then the repo owner would be resposible for the (madness of) rewriting the...