Split up GitHub chapter, add section on GitHub flow

[konradpa]

This splits up the GitHub chapter in Intro and Advanced. Fixes #102.

Also adds Section about GitHub Flow to GitHub Advanced, this discussed in #141.

[lnnrtwttkhn]

Re GitHub Intro chapter

Thanks @konradpa! Minor changes in https://github.com/lnnrtwttkhn/version-control-book/pull/143/commits/f2dbff60a60fc8e80b0f00d911a4db51aad379f9 and a few comments:

• [x] Could you create a new screenshot for "Figure 7.2: Screenshot of the personal access token settings" that zooms in on the relevant details? I think the size is too small. No problem if you need to cut out some of the options from the screenshot.
• [x] Same for "Figure 7.3: Screenshot of creating a new repository"
• [x] Could you check the order of sections in the "GitHub Intro" chapter again? Specifically, we want to avoid mentioning terms before they are fully introduced. For example, I noticed that we talk about "pushing" in the section "Uploading your local repository" but "Pushing" is only introduced in a later section.
• [ ] Change the order of git pull and git fetch. I think git fetch should come first. Oh, just saw that you changed the order? Any specific reason that I can' remember?
• [x] This came up in the GitHub Intro chapter, but should be added to the branches chapter: Viewing remote tracking branches. I think we should add a reference for that command to the branches chapter, saying that this will become more relevant once we start adding remote repositories (e.g., provide reference to the GitHub chapter).

[lnnrtwttkhn]

Re GitHub Advanced

Thanks again @konradpa! A few changes in 7e14647 and comments:

• [x] Add a screenshot of a pull request on GitHub. Maybe use our version control book as an example repository.
• [x] Update the chapter summary in the YAML header, see #146

[konradpa]

Thanks for reviewing @lnnrtwttkhn! I added/fixed your suggestions. Except for the fetching/pulling sequence, since I think pulling is used more commonly also more intuitive, so it makes sense to start with it. Im also open for changing it though

[konradpa]

I also customized code boxes like discussed in #168 + #171. And fixed #185 (Instructions for cloning in different folder) @lnnrtwttkhn

[lnnrtwttkhn]

hi @konradpa, I just reviewed the github intro chapter again, very nice! Two thoughts:

• [x] I think we should think again about the order of pull, push, clone and fetch and tune it to what makes most sense for the course. I would say: push, edit changes remotely, clone, pull and fetch.
• [x] generally, the part of editing a file on github is partly repeated in different sections of the chapter. there should be one section about this and it should be more general and not only apply to the README file. in our course, we will have the scenario where people upload an existing repository from local and likely don't have a README.
• [x] idea for exercise: create a README on github manually (don't initialize the rep with it)
• [x] idea for exercise: instead of git pull, run git fetch and then git merge to see that it's the same end result.

will continue reviewing the advanced chapter later.

[lnnrtwttkhn]

I think we've worked long enough on this and we need to merge before the next session.

Thanks your the great work on this PR @konradpa!