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

fix tab and typo push_githubdesktop images

Browse source
This commit is contained in:
Tom van Woudenberg 2024-11-28 08:59:13 +01:00 • committed by GitHub
parent 27e1e0ee76
commit 4e31ab3beb
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 4 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

1
book/workflows/branches.md
View file

@ -83,6 +83,7 @@ name: Clone_GitHub
Clone using SSH Clone using SSH
``` ```
``````
``````{tab-item} ... GitHub through GitHub Desktop ``````{tab-item} ... GitHub through GitHub Desktop
1. Open the repository that you would like to clone. In the top bar on the right, you will a green button called `<> Code`. 1. Open the repository that you would like to clone. In the top bar on the right, you will a green button called `<> Code`.

24
book/workflows/edit_book.md
View file

@ -197,17 +197,11 @@ After committing, click the 🔄 button to push our changes to the remote reposi
3. Add changes to Git-timeline locally (committing). In the field that says `Summary(Required)`, write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, click the blue button `Commit to repository`. 3. Add changes to Git-timeline locally (committing). In the field that says `Summary(Required)`, write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, click the blue button `Commit to repository`.
4. Now we need to add changes to GitHub/GitLab. This is called pushing to the local repository. After committing, the following screen will pop up. Click on `Push Origin`. 4. Now we need to add changes to GitHub/GitLab. This is called pushing to the local repository. After committing, click on `Push origin` in the top bar.
<figure align="center"> <figure align="center">
<img src="figures/Push_GitHubDesktop.PNG" alt="Example Image" width="650"> <img src="figures/Push_GitHubDesktop.PNG" alt="Example Image" width="650">
</figure> </figure>
Alternatively, you can also click on `Push origin` in the top bar.
<figure align="center">
<img src="figures/Push_GitHubDesktop2.PNG" alt="Example Image" width="650">
</figure>
```` ````
````` `````
`````` ``````
@ -313,18 +307,12 @@ Choose one of the options to resolve the merge conflict. You now have updated yo
5. Add changes to Git-timeline locally (committing). In the field that says `Summary(Required)`, write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, click the blue button `Commit to repository`. 5. Add changes to Git-timeline locally (committing). In the field that says `Summary(Required)`, write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, click the blue button `Commit to repository`.
6. Now we need to add changes to GitHub/GitLab. This is called pushing to the local repository. After committing, the following screen will pop up. Click on `Push Origin`. 6. Now we need to add changes to GitHub/GitLab. This is called pushing to the local repository. After committing, click on `Push origin` in the top bar.
<figure align="center"> <figure align="center">
<img src="figures/Push_GitHubDesktop.PNG" alt="Example Image" width="650"> <img src="figures/Push_GitHubDesktop.PNG" alt="Example Image" width="650">
</figure> </figure>
Alternatively, you can also click on `Push origin` in the top bar.
<figure align="center">
<img src="figures/Push_GitHubDesktop2.PNG" alt="Example Image" width="650">
</figure>
```` ````
````{tab-item} ... using 'VS Code in your browser' ````{tab-item} ... using 'VS Code in your browser'
@ -686,16 +674,10 @@ If your book includes interactive element a webserver is required to host the bo
6. Add changes to Git-timeline locally (committing). In the field that says `Summary(Required)`, write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, click the blue button `Commit to repository`. 6. Add changes to Git-timeline locally (committing). In the field that says `Summary(Required)`, write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, click the blue button `Commit to repository`.
7. Now we need to add changes to GitHub/GitLab. This is called pushing to the local repository. After committing, the following screen will pop up. Click on `Push Origin`. 7. Now we need to add changes to GitHub/GitLab. This is called pushing to the local repository. After committing, click on `Push origin` in the top bar.
<figure align="center"> <figure align="center">
<img src="figures/Push_GitHubDesktop.PNG" alt="Example Image" width="650"> <img src="figures/Push_GitHubDesktop.PNG" alt="Example Image" width="650">
</figure>
Alternatively, you can also click on `Push origin` in the top bar.
<figure align="center">
<img src="figures/Push_GitHubDesktop2.PNG" alt="Example Image" width="650">
</figure> </figure>
```` ````
````{tab-item} ... using 'VS Code in your browser' ````{tab-item} ... using 'VS Code in your browser'