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

fixing figures

Browse source
This commit is contained in:
Julie Kirsch 2024-12-10 20:28:15 +01:00
parent 994820cc12
commit 24838b70b0
4 changed files with 9 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
book/features/custom-launch-button.md
View file

@ -96,7 +96,7 @@ The code in the above cell is the `_launch_buttons.yml` file of a repository cal
```{figure} figures/language_button.PNG
---
width: 50%
name:language_button
name: language_button
---
Custom Button
```

4
book/workflows/github_dev.md
View file

@ -5,7 +5,6 @@
```{figure} figures/Online_VS0.PNG
---
name: New File
width: 50%
align: center
---
@ -16,7 +15,6 @@ New File
```{figure} figures/Online_VS1.PNG
---
name: VS Code in Browser
width: 70%
align: center
---
@ -29,7 +27,6 @@ In the bottom left you can see the branch you are working in.
```{figure} figures/Online_VS2.PNG
---
name: GitHub Actions
width: 70%
align: center
---
@ -39,7 +36,6 @@ You will see the latest commit you just did (in this case text). After the pipel
```{figure} figures/Online_VS3.PNG
---
name: Deployed Branches
width: 60%
align: center
---

7
book/workflows/stage_commit_push_vscode.md
View file

@ -3,6 +3,8 @@
For demonstration purposes, we have created a new Markdown file called `new-chapter.md`, which we want to add to the book. Since this is a new file, Git has no knowledge about its existence yet. I.e., the file is *untracked*. To add new files to our repository, we need to *stage* and *commit* them. To do this, open the Source Control menu in the left side bar. Our new file should appear in this menu:
```{figure} ../images/git-new-file.png
---
width: 100%
---
The new file appears in the Source Control menu.
@ -14,6 +16,8 @@ Notice that there is a green letter U placed besides the file, meaning that our
Next, in the field that says "Message", write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, the menu should now look something like this:
```{figure} ../images/git-file-added.png
---
width: 100%
---
The new file has been staged, and we've written a Commit Message.
@ -26,6 +30,9 @@ Now, we are ready to add the changes to the repository. This is done by *committ
In the bottom left corner, next to the branch name, click the "Synchronize Changes" button (the one that looks like this: 🔄, highlighted in the image below) to push the changes to GitLab/GitHub.
```{figure} ../images/git-push.png
---
width: 100%
---
After committing, click the 🔄 button to push our changes to the remote repository.
```

2
book/workflows/user45_check_changes.md
View file

@ -25,7 +25,7 @@ Note: use `--all` for the jupyter-book whenever building a book to make sure the
Where book is the name of the folder containing all the files that make up your book. After `teachbooks` is done running you will get the following:
```{figure} ../figures/buildbook.PNG
---
Output
```
Paste the last line into your browser to see the updated changes.