Merge pull request #36 from devinekask/feature/starterfiles

Feature/starterfiles

Author: SimonVanherweghe

.markdownlint.json

@@ -0,0 +1,4 @@
+{
+  "no-inline-html": false,
+  "line-length": false
+}

src/content/docs/git/basics/git-04-undo.md

@@ -2,6 +2,15 @@
 title: Undo
 ---
 
+<details>
+<summary>Looking for the starting files?</summary>
+
+The ideal way to follow this walkthrough is to go over the previous topics first. If you want to skip to this topic, you can [download the starting files here.](https://github.com/devinekask/workflows-git-steps/archive/refs/heads/step/track-commit.zip)
+
+Be aware that you will have to initialize a git repository first via `git init` in the unzipped folder.
+
+</details>
+
 Whoops, we messed up, what now?
 
 ## Undo changes after staging

src/content/docs/git/basics/git-05-ignore.md

@@ -2,6 +2,15 @@
 title: Ignore files
 ---
 
+<details>
+<summary>Looking for the starting files?</summary>
+
+The ideal way to follow this walkthrough is to go over the previous topics first. If you want to skip to this topic, you can [download the starting files here.](https://github.com/devinekask/workflows-git-steps/archive/refs/heads/step/undo.zip)
+
+Be aware that you will have to initialize a git repository first via `git init` in the unzipped folder.
+
+</details>
+
 It won't be necessary to keep track of all the files in a project folder via Git. For example, it is not a good idea to track a `node_modules` (see later) or `uploads` folder in your repository. Also hidden system files, such as `.DS_Store` are of no use in a repository.
 
 Let us work with an example. Create a dummy project like this:

src/content/docs/git/basics/git-06-branches.md

@@ -2,6 +2,15 @@
 title:  Branching
 ---
 
+<details>
+<summary>Looking for the starting files?</summary>
+
+The ideal way to follow this walkthrough is to go over the previous topics first. If you want to skip to this topic, you can [download the starting files here.](https://github.com/devinekask/workflows-git-steps/archive/refs/heads/step/ignore.zip)
+
+Be aware that you will have to initialize a git repository first via `git init` in the unzipped folder.
+
+</details>
+
 You can also use branches via Git.
 
 You can use branches to:

src/content/docs/git/collaboration/collab-01-github-push.md

@@ -100,6 +100,15 @@ Remember to choose the SSH option (instead of the HTTPS option) when cloning a r
 
 ## Create repository & first push
 
+<details>
+<summary>Looking for the starting files?</summary>
+
+The ideal way to follow this walkthrough is to go over the previous topics first. If you want to skip to this topic, you can [download the starting files here.](https://github.com/devinekask/workflows-git-steps/archive/refs/heads/step/branches.zip)
+
+Be aware that you will have to initialize a git repository first via `git init` in the unzipped folder.
+
+</details>
+
 Login to your GitHub account, and click the "New repository" button. Choose a name for your repository and click the "Create Repository" button.
 
 Don't add a `readme.md` or a `.gitignore` file yet. Since we will sync this repo with an existing one (the one we created in a previous chapter) things will get complicated if there are files on both ends. (It is definitely possible to fix this, but we won't go in to that now) If you would start completely from scratch, this wouldn't be an issue.

src/content/docs/git/collaboration/collab-02-pull-rebase.md

@@ -2,6 +2,15 @@
 title:  Pull
 ---
 
+<details>
+<summary>Looking for the starting files?</summary>
+
+The ideal way to follow this walkthrough is to go over the previous topics first. If you want to skip to this topic, you can [download the starting files here.](https://github.com/devinekask/workflows-git-steps/archive/refs/heads/step/github-push.zip)
+
+Be aware that you will have to initialize a git repository first via `git init` in the unzipped folder.
+
+</details>
+
 ## Pull existing repository
 
 Once a repository has been created, and is on a server like GitHub, you can also download it from other computers/locations. Downloading the repository for the first time is done via the `git clone` command. From then on you can get updates via the `git pull` command. `git pull` is the inverse of `git push`, and you will use it to pull in updates you don't already have locally.

src/content/docs/git/collaboration/collab-03-merge-conflicts.md

@@ -2,6 +2,15 @@
 title: Merge conflicts
 ---
 
+<details>
+<summary>Looking for the starting files?</summary>
+
+The ideal way to follow this walkthrough is to go over the previous topics first. If you want to skip to this topic, you can [download the starting files here.](https://github.com/devinekask/workflows-git-steps/archive/refs/heads/step/pull-rebase.zip)
+
+Be aware that you will have to initialize a git repository first via `git init` in the unzipped folder.
+
+</details>
+
 So far we have only made changes in separate files. However, it can happen that you have made changes to the same file with 2 people, and that a conflict occurs.
 
 In the `project` folder, edit the text in `hello.txt` and push it to the remote repository: