Compare commits

...

7 Commits

Author SHA1 Message Date
waldek f7b945683c adds some doc 2021-04-02 16:12:19 +02:00
waldek 97142426f5 Merge branch 'master' of https://gitea.86thumbs.net/waldek/documentation
this merge comes from the title change test in class
2021-04-02 14:03:00 +02:00
waldek 914437bf5a actual doc added 2021-04-02 14:02:44 +02:00
Hugo ba4979eba2 My first commit on waldek/Docu 2021-04-02 11:30:24 +02:00
waldek d34906f9f2 brings experimental to master 2021-04-02 10:49:53 +02:00
waldek 436c21ec65 master commit message 2021-04-02 10:11:23 +02:00
waldek 0d4b4f620b future commit message 2021-04-02 10:07:40 +02:00
1 changed files with 61 additions and 2 deletions

View File

@ -1,4 +1,4 @@
# This is my documentation for the Linux course # This is my documentation for the best course ever
## Matrix ## Matrix
@ -21,5 +21,64 @@ A general overview of *how* git works can be seen in th diagram below.
### Gitea ### Gitea
You can log in to our personal gitea [here](https://gitea.86thumbs.net). You can log in to our personal gitea [here](https://gitea.86thumbs.net).
Feel free to make as many repositories as you want to!
If you want to try out how multiple accounts work together you can create secondary accounts for yourself as well, or invite someone from class to test things out together.
### Practice
As practice you can do the following two exercizes.
I would advise to start with the first one.
Once you understand how branches work you could try the second game which is more riddles than git.
The third exercize is fully online and was an in class suggestion.
* [fracz](https://gitexercises.fracz.com/)
* [git-game](https://github.com/git-game/git-game)
* fully [online](https://www.katacoda.com/courses/git/1) exercizes
While doing the exercizes it is a *good* idea to keep track of the documentation and tutorials you find online.
At the bare minimum, make a list of links for future reference.
A more complete approach would be to create dedicated paragraphs for each exercize.
### Fracz
#### EX 1
This is a pretty simple one.
There is a commit waiting to be pushed, all you have to do is push it.
Remember, with this game it's not **push** but **verify**.
```
git verify
```
Once you verify and the solution is passed, you can go to the next exercize by executing:
```
git start next
```
If at some point you mess up, you can restart the exercize by typing:
```
git start
```
#### EX 2
Only add one file to the repository.
A quick tutorial on how to add files can be found [here](.
#### EX 3
#### EX 4
#### EX 5
#### EX 6
#### EX 7
#### EX 8
#### EX 9
this is my experimental info