Added exercise 5

This commit is contained in:
Tom van Woudenberg 2024-12-13 17:36:56 +01:00
parent a7b71c813c
commit a180e5ab3a
5 changed files with 33 additions and 5 deletions

View file

@ -2,11 +2,11 @@
By now, we've covered the essentials: content files, `_toc.yml` and `_config.yml`. But what if you want to make some changes but don't want to share them directly with the general public of your book website? Or what if you have some work-in-progress that you want to share with colleagues? You need a version of your book! Let's try and do that! Later on, you'll probably want to merge your newest version back into the original book. That's what we'll do in [](./005.md).
Can you make a new branch of your book with an additional file `file_on_new_version.md` and view it online?
> Can you make a new branch of your book with an additional file `file_on_new_version.md` and view it online?
1. Add a new Issue to let people know you're working on something by going to your repository (`https://github.com/<your_username>/<your_repo_name>`) - {octicon}`issue-opened;1em` `Issues` - `New issue` (note that is not required for making your own version, but it's good practice so that people know where you're working on)
2. Add a title and description, eg. `Added some content`
3. On `Assignees`, click `Assign yourself
3. On `Assignees`, click `Assign yourself` to make clear that you feel responsible for this issue.
4. Click `Submit new issue`
5. In the new window, under `Development`, click `Create a branch` (note that you could also make branches in other ways, but in this way it's directly linked to the issue). A 'branch' is a separate version of the book which keeps the link with the original book.
6. Use the default options and click `Create branch`