Docs should get built automatically

[shardros]

Brief

As a Shepherd patch developer.
I would like the docs to be automatically updated from the website whenever the website changes.
So that

• I don't have to remember to update them
• We know that nothing has changed since they were last updated to make them not updatable

Notes

Whenever the docs are changed in the website repo they should trigger some kind of GitHub Action build step which should push an updated version to master of shepherd.

We should be careful about pushing large amounts of binary data to shepherd e.g. images. I already make sure to always clone with --depth 1.

[casheww]

This requires cloning shepherd, which I don't think is possible from a GitHub Action until shepherd is made public, so I think this is waiting on #30 . Once that's been done and shepherd is public, I'm happy to continue working on this :)

[shardros]

I don't know if this is a good idea to do automatically but we will probally need to make sure that every PR is rebased before merging to master otherwise we might lose changes in the compiled output. In #30 right now

[Minion3665]

This requires cloning shepherd, which I don't think is possible from a GitHub Action until shepherd is made public, so I think this is waiting on #30 . Once that's been done and shepherd is public, I'm happy to continue working on this :)

It would be possible to use secrets to store a PAT (or a deploy key?) and clone using that, but I agree that it would probably be better to fix and merge #30 instead

[shardros]

Now unblocked 🎉