chore: setup semantic commit bot

[HonkingGoose]

What would you like to be able to do?

It might be nice to check if the PR titles are using Semantic Commits on this repo as well?
That would prepare us for if we ever want to release versioned docs (though this is hard to to in Docusaurus v2, and not recommended by the Docusaurus devs...)

If anything, having semantic commits will probably make it easier to search the logs for relevant changes.
And we're then consistent with the format we use for the main Renovate bot repo.

Did you already have any implementation ideas?

We could copy/paste the semantic bot from: https://github.com/renovatebot/renovate/blob/master/.github/semantic.yml
The repository admin probably needs to tinker in some configuration menu for the bot, to ensure the bot is allowed to run on this repo.

[HonkingGoose]

That would prepare us for if we ever want to release versioned docs (though this is hard to to in Docusaurus v2, and not recommended by the Docusaurus devs...)

We decided to stay with Material for MkDocs, which supports versioning for the documentation. ¹ It sounds tricky to get versioning working in the docs site though.

I remember discussing somewhere that we want to build our docs in the main Renovate repository, and bundle the docs in the release files for Renovate. So people can always grab the docs from the GitHub releases page, for the Renovate version that they're using.

• Use released docs package from renovate to generate docs #108

Footnotes

1. https://squidfunk.github.io/mkdocs-material/setup/setting-up-versioning/ ↩

[HonkingGoose]

Let's keep things as they are now. We can always set up Semantic Commit checking and Semantic Release later.