Waldir Pimenta
Also success messages, e.g. uploading images. For future reference, this was prompted by discussion around #56.
@jart please refrain from commenting on this repository if you can't disagree with people in a civil manner. ps - attitudes like that displayed in your comment is precisely why...
Since the opening comment didn't mention it, I think it might be useful to keep track of the suggestions specific to mwclient made during that evaluation project: https://www.mediawiki.org/wiki/API:Client_code/Evaluations/mwclient#Suggested_TODOs Quoting below...
> Any thoughts on this, @waldyrious ? I never really user mwclient as a library in another project (I only made quick scripts here and there, back when I dabbled...
> I have not the "Allow edits from maintainers" link on this PR. Maybe it's only when we create a new-one ? You should be able to see it as...
> Maybe it's because the repo is inside our organization namespace instead my personal namespace. Ah, that makes sense. Yeah, it should be it. Thanks for digging up that info!...
How about [python-semantic-release](https://python-semantic-release.readthedocs.io/en/latest/) ([repo](https://github.com/relekang/python-semantic-release))? It's a Python port of the [semantic-release](https://www.npmjs.com/package/semantic-release) npm package, which provides a way to semi-automatically determine the version [based on the contents of the commit messages](https://github.com/semantic-release/semantic-release#how-does-it-work)...
Yeah, that was my concern as well. I believe the changelog is generated from PR titles rather than commits, so it shouldn't be hard to edit them after the fact...
/cc-ing @lgonzalezsa from #196
When we start using Sphinx, the [documentation coverage module](http://sphinx-doc.org/ext/coverage.html) will probably be useful to collect and display stats about how much of the code still needs documentation. cf. #40.