steps

Steps for the GUI Presentation

1.) Do the presentation!
2.) Give out Glossary!

GitHub Desktop
3.) Open GitHub Desktop
4.) Clone this repo
5.) Look in the History of "Ein kleines Gedicht"
6.) Show the diff
7.) Make a new Branch, everybody can make his own language
8.) Tanslate the thing 
9.) Commit
10.)Push
11.)Pull the others
12.) Make a few little changes but do NOT commit!
13.) Try Change the branch
14.) Get a message (and don't change)
15.) Stash
16.) Look into the file, the change is gone!
17.) Make a diffrent change and stash
17.) b) Notice that you can only stash once! This is a drawback of GitHub Desktop!
18.) Change the branch and not fail
19.) Unstash
20.) Create a pull request!
GitHub Desktop CAN NOT "go back in time" or have big stashes or something in this direction. It can do just the basic but can do them very very good!
This might help a bit for the ends of the branches:
https://github.com/fprott/git_test/compare/master@%7B1day%7D...master

21.) Do some stupid changes
22.) Delete them

GitHub
1.) Go to GitHub
2.) Log in
3.) Find your repo
4.) Look into the readme
5.) Look into the pi.txt file
6.) Go back in time trough the History with blame
7.) Notice that this History is much smaller then the normal History
8.) Look at the first entry
9.) Go into text 
10.) Click on History
11.) Mind the diff (unified and split!)
Warning, GitHub is not the best side for this!
12.) Look into the wiki
13.) Look into the issues
14.) Skim the stastics
15.) Look into the manage access
16.) Look & do the pull request onto master! (Reject for fun)

GitKraken
1.) Clone the repo or use an existing repo
2.) Explain the need for issue tracker but do not elaborate too much
3.) Look at the tree
4.) Stage and commit a little change
5.) Push
4.) Compare three things in the tree (keep in mind that the file must exist)
5.) Take a few minutes and learn the diff tree
6.) Make some changes
7.) Stage changes
8.) Look how you can unstage changes!
9.) Push
10.)  Make a new branche, look how it works
11.) Change something
12.) Switch branches after save
13.) Look how the files are changing with
14.) Merge (Explain the diffrence to rebase and why rebase is kind of bad here)
If you do rebase then you want You want the rebase BRANCH onto master !
You really shouldn't, it looses the master behind!
15.) Branch again
16.) Edit an existing line of code! To break something!
Edit an existing line of code in two branches after the merge! This will cause a confilct!
17.) Merge, this will fail!
18.) Resolve the confilct!
19.) now make a comit that you do not like
20.) Delte it!
21.) Now make a file that you do not like, and not stage it!