Tie docs to releases

[dbanty]

Tie docs to releases

I propose a third idea.
what if there was a branch exclusively dedicated to documentation releases? let's call it documentation.

main could still be the default branch, but every time you gotta update the documentation, you rebase the documentation branch on main (or merge into it, but i like rebasing for this case). This way documentation is no longer tied to the default branch.

This does add an extra step, but knope should be able to easily handle this workflow ^^

[dbanty]

That's a good idea, then the default workflow of bundling upcoming changes together works well (especially if we automate that rebase onto documentation), but if there's a docs-only change to release in the meantime that PR could be merged straight into documentation so it doesn't have to wait for a release.