untagged master commits build and overwrite the latest version
other commits could build and overwrite the branch-name version
Note: point (3) would be intended for us to be able to test new documentation pages, see generated docs before releasing, etc. - so for this to work as intended, we would have to remove the corresponding docs page when merging a branch, which I don't think we can reasonably automate.
It might be easier for us to not publish branch docs and build & test them locally instead.
A GH page is easy to setup and we now have a test page at https://trick-17.github.io/clang-build which is published from https://github.com/Trick-17/clang-build/tree/gh-pages
The goals would be
latest
versionbranch-name
versionNote: point (3) would be intended for us to be able to test new documentation pages, see generated docs before releasing, etc. - so for this to work as intended, we would have to remove the corresponding docs page when merging a branch, which I don't think we can reasonably automate. It might be easier for us to not publish branch docs and build & test them locally instead.