Merge branch 'main' into 'publish'

Multiple branches in GitHub

See merge request interactivetextbooks-citg/jupyter-book-manual!46
This commit is contained in:
Tom van Woudenberg 2024-03-04 12:18:45 +01:00
commit f66a935e37
3 changed files with 15 additions and 3 deletions

3
.gitignore vendored
View file

@ -133,4 +133,5 @@ _build/
_contents/
# Jupyterlite
_output/
_output/
book/.jupyterlite.doit.db

Binary file not shown.

View file

@ -29,6 +29,17 @@ Wait a few minutes for the website to be deployed, if you're curious, have a loo
![alt text](../images/image-8.png)
When the workflow has finished, visit your build book at https://<username>.github.io/<repository_name> (case sensitive). For our example it is: https://dummystudent-Tom.github.io/My_own_book:
When the workflow has finished, visit your build book at `https://<username>.github.io/<repository_name>` (case sensitive). For our example it is: [https://dummystudent-Tom.github.io/My_own_book](https://dummystudent-Tom.github.io/My_own_book) :
![alt text](../images/image-9.png)
---
It is possible to have multiple versions of a book published at once, by creating another Git branch (e.g. `draft` or `dev`).
For each branch, the respective book is published at `https://<username>.github.io/<bookname>/<branchname>`.
Technical note: for convenience, just `.../<bookname>/` redirects to `.../<bookname>/book/`, which is itself an alias (a symlink) for
`.../<bookname>/main/`.
To learn more about how we do this, please see the [GitHub Actions documentation](https://docs.github.com/en/actions) and our deployment pipeline configuration file `.github/workflows/deploy-book-ghpages.yml` [here](https://github.com/TeachBooks/template/blob/main/.github/workflows/deploy-book-ghpages.yml).
![alt text](../images/image-9.png)