Skip to content
Snippets Groups Projects
Verified Commit 43ad08cb authored by ck85nori's avatar ck85nori :railway_track:
Browse files

intro and motivation more or less done

parent 26ce5822
Branches
No related tags found
No related merge requests found
...@@ -20,45 +20,100 @@ ...@@ -20,45 +20,100 @@
<div class="reveal"> <div class="reveal">
<div class="slides"> <div class="slides">
<section id="title" data-markdown> <section>
# git basics <section id="title" data-markdown>
# git basics
## for beginner-level git users
note: notes:
- if you have questions ask them right away - if you have questions ask them right away
- hand out cheat sheets - hand out cheat sheets later, no need to write stuff down
</section> </section>
<section> <section id="intro-objectives" data-markdown>
<section id="intro" data-markdown> ## objectives
# intro
- teach you to fish
- hands-on experience
- use version control!
- collaborate!
</section> </section>
<section id="intro-about-me" data-markdown>
## about me
- scientific computing support @ idiv since 2014
- happy git user since 2010
> There will never be a better version control system than git.
>
> -- Christian Krause, Chemnitz 2017
</section>
<section id="intro-about-today" data-markdown>
## about today
be able to ...
1. use git in **ALL** your projects
2. collaborate with each other
... that is mission accomplished.
notes:
- there is time for fancy stuff later
- take a few weeks getting used to git
- delay is good to grow your own experience
- growing pain is how we learn
</section>
<section id="intro-you" data-markdown>
## about you
![people](img/people.jpg)
name, job, git experience, why git?
</section>
<section id="intro-about-git" data-markdown>
## about git
1. **records changes to a repository**
content, who, when, message
2. **best tool for the job**
technical, usability, community
notes:
- the fact that content is organized in files and directories is
only incidental
- for git to be useful, content has to be text
</section>
</section>
<section>
<section id="motivation" data-markdown> <section id="motivation" data-markdown>
## motivation # motivation
> Why should I use git? > Why should I use git?
- boss
- project version history
- project management
- show scenarios
</section> </section>
<section id="intro-motivation-avoid-mess" data-markdown> <section id="motivation-avoid-mess" data-markdown>
## motivation #1 ## motivation #1
### avoid mess ### avoid mess
![blah](img/draft_mess.png) ![blah](img/draft_mess.png)
</section> </section>
<section id="intro-motivation-want-structure" data-markdown> <section id="motivation-want-structure" data-markdown>
## motivation #1 ## motivation #1
### want structure ### want structure
![blah](img/gitk-pretty-history.png) ![blah](img/gitk-pretty-history.png)
</section> </section>
<section id="intro-motivation-playground" data-markdown> <section id="motivation-playground" data-markdown>
## motivation #2 ## motivation #2
### throw-away playgrounds ### throw-away playgrounds
...@@ -72,7 +127,7 @@ ...@@ -72,7 +127,7 @@
- (done right) decision based on regression testing - (done right) decision based on regression testing
</section> </section>
<section id="intro-motivation-collaboration" data-markdown> <section id="motivation-collaboration" data-markdown>
## motivation #3 ## motivation #3
### collaboration made easy ### collaboration made easy
...@@ -82,7 +137,7 @@ ...@@ -82,7 +137,7 @@
notes: notes:
- demo GitLab - demo GitLab
- [go to project](https://git.idiv.de/sc/edu/git-seminar) - [go to project](https://git.idiv.de/sc/edu/git-seminar)
- check if still in master - check if typo still in master
- edit - edit
- change **target branch** to create merge request - change **target branch** to create merge request
- commit message: - commit message:
...@@ -93,7 +148,7 @@ ...@@ -93,7 +148,7 @@
``` ```
</section> </section>
<section id="intro-motivation-creative-use" data-markdown> <section id="motivation-creative-use" data-markdown>
## motivation #4 ## motivation #4
### the creative use of git award ### the creative use of git award
#### goes to Michael Schilli #### goes to Michael Schilli
...@@ -120,7 +175,7 @@ ...@@ -120,7 +175,7 @@
### use version control for ### use version control for
# *everything* # *everything*
| common | less frequent | esoteric | | common | less frequent | esoteric? |
| ------------ |:---------------:| ---------------:| | ------------ |:---------------:| ---------------:|
| software | presentation | youtube | | software | presentation | youtube |
| blog | paper / thesis | soundboard | | blog | paper / thesis | soundboard |
...@@ -134,34 +189,31 @@ ...@@ -134,34 +189,31 @@
## motivation #a ## motivation #a
### automation ### automation
> see advanced seminar
- software testing - software testing
- build app and deploy to app store - build app and deploy to app store
- put presentation on web server - put presentation on web server
</section>
<section id="audience" data-markdown>
## audience
- beginner-level git users *(see advanced seminar)*
</section> </section>
</section>
<section id="goals" data-markdown> <section>
## goals <section id="start" data-markdown>
# let's get started
- get you started notes:
- git is simple and complex
- git seems complex for 2 reasons:
- you're unfamiliar with command line
- there are a lot of choices
- only X (TODO) theory pages
- I'm gonna dumb it down for you
- aka we'll stick to the simple parts
</section> </section>
<section id="cheatsheet" data-markdown> <section id="cheatsheet" data-markdown>
# [cheat sheet](https://idiv-biodiversity.github.io/git-cheat-sheet/) # [cheat sheet](https://idiv-biodiversity.github.io/git-cheat-sheet/)
</section> </section>
</section>
<section>
<section id="start" data-markdown>
# let's get started
</section>
<section id="cli" data-markdown> <section id="cli" data-markdown>
## command line ## command line
......
img/people.jpg

239 KiB

0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment