You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, whichever deployment is last will take over gh-pages. We can think how to make it work during the tutorial. Could just set them deploy from separate branches: and keep the Jupyter Book on except when we want to show the Create Webpage Example. On the participants fork we should make sure they have the create website deployment active only, since they do not need to rerender the jupyterbook website. Any better way to do this? I can also show things from a fork, and keep the uwescience one intact.
The text was updated successfully, but these errors were encountered:
Yes, currently GitHub's deploy-pages action is "atomic" so it's all or nothing and not possible to just create a subpage on top of existing content (see actions/deploy-pages#349)
For the tutorial I think it makes sense to show [.github/workflows/create_website.yml] on your fork to avoid overwriting the book (.github/workflows/create_website.yml)
You could add if: github.repository == 'uwescience/SciPy2024-GitHubActionsTutorial' under runs-on below to only deploy the book in this repository and not on participant forks:
Currently, whichever deployment is last will take over gh-pages. We can think how to make it work during the tutorial. Could just set them deploy from separate branches: and keep the Jupyter Book on except when we want to show the Create Webpage Example. On the participants fork we should make sure they have the create website deployment active only, since they do not need to rerender the jupyterbook website. Any better way to do this? I can also show things from a fork, and keep the
uwescience
one intact.The text was updated successfully, but these errors were encountered: