Add github workflow file to deploy docs to pages#59
Conversation
|
Thanks @thomaszwagerman I made the changes - does that look right?
|
|
I think under Branch (it might do that automatically though, I can't remember) |
|
I think @JimMadge and I would be happy to move this repo to TTW's org if there's no objections from the rest of the hackday team? |
Can be reintroduced when we have capacity to address the warnings
|
If we do a proper GitHub migrate, I think we retain the issues, PRs, and so on. Might need to give @RayStick extra permissions temporarily on @the-turing-way to do that. If you let me know if/when you'd like to do that I can sort it out 👍. |
|
@JimMadge I requested a transfer to your account! (@sgibson91 it did not work for you, probably because you have a fork of the same name). Hopefully this allows you to then bring it to TTW og😌 |
|
I think changing my or @sgibson91's role to Owner is probably the best solution. That way we can avoid transferring the repo twice. Or, can you request a transfer directly to The Turing Way? |
|
Sure. I need write access to transfer direct to TTW org. I didn't see an option to add you as an owner, EDIT: A personal public GH repo doesn't seem to have as many granular options for permissions for collaborators. It needs to be a repo within an organization for that |
|
@RayStick I've sent you an invitation to the org, that should give you the permission to create repos (and hence transfer this repo 🤞). Let me know if that works. |
|
Done 🥳 |
|
@sgibson91 @JimMadge now that this is on TTW - do feel free do adapt the docs/hosting methods completely as you see fit, if there is some standardised theme/hosting infrastructure this should align to etc |
And let me know if I can help with the docs in any way :) |
JimMadge
left a comment
There was a problem hiding this comment.
Some suggestions.
Most importantly, I think we shouldn't have a different build command here than in the pyproject.toml.
GitHub Pages seems sensible to me. |
Co-authored-by: Jim Madge <jim+github@jmadge.com>
Co-authored-by: Jim Madge <jim+github@jmadge.com>
Co-authored-by: Jim Madge <jim+github@jmadge.com>
Co-authored-by: Jim Madge <jim+github@jmadge.com>
Co-authored-by: Jim Madge <jim+github@jmadge.com>
|
What needs to be done to get this documentation PR merged? It is out of date now, so I am hesitant to be the one that reviews and merges it - @sgibson91 and @JimMadge what do you think? |

Publishing docs to Github Pages on push to main.
A repeat of #51, which was closed without merging by accident during the hectic last few minutes of the hack day!
This will require @RayStick to configure publishing source in the repo settings.
Also see mkdocs publishing instructions.
If this is moving across to TTW(?) it might be easier to hold off merging until that is done?