Add additional action to publish docs of main

[sascha-wolf]

Currently docs only get published on release.

It would be great if we could publish the docs for main on each push/merge.

Questions

• Which version would these docs have?

[joseemds]

Hi, i would like to try this one, about the version name. what about: next or x.y.z-dev?

[sascha-wolf]

Hey @joseemds thanks for considering to pick this up.

The version needs to follow the constraints laid out in the docs of the Version module which follow the ones from semver.org.

Without going into details: this makes next an impossible option although I do think it'd be a good choice.

The best next option I can see would be <next version>-dev which right now (with the current version being 1.4.1) would be 1.4.2-dev. That would require the following steps:

1. figure out the current version (should be possible through git describe --first-parent --tags --abbrev=0 which returns v1.4.1 right now on main)
2. figure out the next semver version (maybe there's a GitHub Action we can use here?)
3. write the calculated version to the version file and publish to Hex (check the release action for details on this)

Does this make sense and give you enough pointers to figure things out, @joseemds?

[joseemds]

Hi @sascha-wolf, yes it does, thanks for the guidance