From 750102c78fc1f3ee1957204a308d325e43c2ab2b Mon Sep 17 00:00:00 2001 From: Katia Gatt Date: Mon, 22 Sep 2025 19:02:26 +0200 Subject: [PATCH] part 1 --- book/extension_exercises/015.md | 38 +++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 book/extension_exercises/015.md diff --git a/book/extension_exercises/015.md b/book/extension_exercises/015.md new file mode 100644 index 0000000..12eb9e7 --- /dev/null +++ b/book/extension_exercises/015.md @@ -0,0 +1,38 @@ +# Exercise: Deploy Book Workflow + +The **Deploy Book Workflow (DBW)** automatically builds and publishes your TeachBook whenever changes are pushed to your repository. If you started your book from the TeachBooks Template, this workflow is already included. + +With this workflow, readers can see your latest book version online without manual intervention. This exercise will guide you through triggering the workflow, configuring branch-specific builds, and customising deployment options. + +::::::{topic} Exercise objective +Can you trigger, configure, and monitor the Deploy Book Workflow to publish your TeachBook automatically? +:::::: + + + +## Trigger the workflow + +1. Make a small edit in any page of your book (for example `book/intro.md`). +2. Commit the change and push it to the `main` branch. +3. Open the **Actions** tab of your repository. You should see a workflow called *Deploy Book* running. +4. When it finishes, visit the URL: + + ```` + https://.github.io// + ```` + + to see the updated book. + + +5. The workflow can also be triggered in a separate branch. Create a new branch, e.g., `draft-chapter`. +6. Push a change to this branch. +7. The DBW automatically builds a version of your book for that branch, available at: + + ```` + https://.github.io//draft-chapter/ + ```` + +```{tip} +Branch-specific builds are useful for previewing work in progress without affecting the main book. +``` +