publish docs automatically

[jeichler]

currently the docs are fairly behind the current main branch.
Ideally docs are published after a merge into the main branch (kinda like version "latest").

thoughts?

[djdanielsson]

I agree, it should be on commit it re-publishes them

[ericzolf]

My initial idea was to push regularly versions, which would trigger the build, but I agree that it doesn't really work well and was probably over-engineered.

[ericzolf]

I just pushed v2022-12-15-12 so we're up-to-date again, but still agreed that we don't need the overhead.

[ericzolf]

IMHO, what needs to be done:

• update the pipeline to re-create the website on merged PRs resp. modified main branch
• add a variable/placeholder in the documentation and some code to automatically do versioning based on Git commit date (like CER does)

[Fale]

@ericzolf what do you mean by "CER" in this context?