admin2/template
1
0
Fork 0
mirror of https://github.com/TeachBooks/template.git synced 2026-11-12 22:25:52 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update 004.md

Browse source
This commit is contained in:
Tom van Woudenberg 2025-03-04 17:05:29 +01:00 • committed by GitHub
parent 903e7e92db
commit 063c886000
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
book/exercises/004.md
View file

@ -9,8 +9,8 @@ Can you make a new branch of your book with an additional file `file_on_new_vers
1. Add a new Issue to let people know you're working on something by going to your repository - {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` 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.
4. Click `Create`
5. In the new window (inside your just created issue), 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`
7. Ignore the `checkout in your local repository`- popup for now (later on you'll know what this is and how to use it)
8. Go to `Code` - {octicon}`git-branch;1em` `main` and click on `1-<your_issue_title>` to open your branch.
@ -25,4 +25,4 @@ Before moving on to the next exercise, make sure you understand the following:
- What is the purpose of creating a new branch in your repository?
- Why is it good practice to create an issue before starting work on a new feature or change?
- How can you view the changes made in your new branch online?
```
```