Daniel Thwaites

As a workaround you can modify [`build_command`](https://python-semantic-release.readthedocs.io/en/latest/configuration.html#build-command) to add your files to the dist folder; however I think this would cause the additional files to also be uploaded to PyPI.

@jkowalleck done :)

When I added the ability to attach distributions to GitHub Releases, I'd never worked with GitLab (and still never have), so I left it out. I'm happy to convert this...

Looking at that link you sent, maybe it'd be better to add more comprehensive support for monorepos instead of just the changelog titles.

Unreleased pairs of commits should be ignored. If the original commit *was* released, would you expect the revert commit to trigger a second release? If so, what level of version...

Perhaps this should be left open, since it could be an important feature for other users?

As Python Semantic Release only needs to check commits which occurred after the latest release, the most recent version tag is used as a boundary. This behaviour is not affected...

If tags are always created, regardless of the `version_source` setting, then it would make sense to only use those to read the version.

I think we'd be better with a separate organisation if there are going to be multiple repositories. That way people could use the organisation homepage to search for plugins. >...

The commitlint failure is because your commit message starts with a capital.