release-automation

Most of the documentation has been rewritten recently. The content minimum content we need is there but there is a lot that can be done to improve it.

If you'd like to contribute to the semantic-release project, helping with the following would be much appreciated:

• Fix typo, misspelling and gramatical mistakes
• Improve language: make short and simpler sentences, improve clarity
• Harmoniz

... if maybe we could one day completely go for ConfigUpdater as template systems for setup.cfg. I think it would save us some code and avoid workarounds like this.

Originally posted by @FlorianWilhelm in pyscaffold/pyscaffold#509 (comment)

We use the template just as a structure for the sections, default values and comments, but not do any str

We have a workflow where we want do generate the release notes only from pull requests and mention the pull request author. I have found no way to do this yet...

The files on PyPI have these hash values:

• SHA256
• MD5
• BLAKE2-256

If print the hash values, people can easily verify whether the file on PyPI was automatically uploaded by CI script.
It is best to print a pretty-print table.

See "Optimizing storage" issue: