Bit overdue on my part - due to quirks of gh actions changes on the master branch will not trigger workflows on the docs-source branch so it needs to be defined here as well. Good news is, we can have different triggers.
I've set this up to rebuild docs either on-demand or when a release is published. If you wanted you could replace L4-5 with
push:
branches: [ master, docs-source ]
similar to on the docs-source branch. This would automatically rebuild docs every commit which could be desirable but in theory may make the docs a bit unstable and ahead of the released library. Your call how much you care :)
Bit overdue on my part - due to quirks of gh actions changes on the master branch will not trigger workflows on the docs-source branch so it needs to be defined here as well. Good news is, we can have different triggers.
I've set this up to rebuild docs either on-demand or when a release is published. If you wanted you could replace L4-5 with
similar to on the docs-source branch. This would automatically rebuild docs every commit which could be desirable but in theory may make the docs a bit unstable and ahead of the released library. Your call how much you care :)