Git as is

Let’s move to the shell terminal/console/command line, if you are on Windows open GitBash.

Is Git there?

git

Exercise 1

• what is your version of Git?
• what happens when you type git --help?
• what happens when you type git -h?

Introduce yourself

When we use Git for the first time, we need to configure a few things.

Exercise 2

Use your name or nickname and the email associated with your GitHub account, for consistency.

$ git config --global user.name "Sam Claes"
$ git config --global user.email "sclaes@email.com"

We can add more options, but these are the two basic ones. You only need to do this the first time that you use Git. You can then check your options with:

git config --list

New Project

Create a folder on your preferred location.

$ mkdir firstGit
$ cd firstGit

Exercise 3

Once inside the folder, initiate a repository where Git can store versions of your files

git init

You need this every time you add a new project folder. Repositories should have a top level track of changes.

• Does someone knows how to see hidden files? - We will find something interesting.

Thing 1. Let’s you tell the story of your project

git status

Exercise 4

We can create one file, using Atom editor. A good file to start with is a README.md file. (Learn more about the README.md tips)[https://www.makeareadme.com/] and (template)[https://readme.so/].

atom README.md

Check the story of your Project

git status

Track of changes time-stamp

git add
git status

• What does the message says?

Exercise 5

Add some the changes following the message instructions

git commit -m "adding a README.md"

Check the story of your Project

git status

Exercise 6

• On the README.md file write your name and the date
• Create a code file in your preferred language
• On the code file add one or two lines of code

Check the story of your Project

git status

Exercise 7

What is our new status?

git commit -a 

Recap

• git status
• git add
• git commit -m
• git status

repeat three times!

Break 10 min

Git history

We can ask Git to show us the project’s history using git log

Exercise 1

• Do you remember what was the name of this long character string?
• Add “# My first Git Project” at the top of your README.md file
• Check the differences before a commit with git diff
• Save your changes (Recap)
• Check the differences after the commit with git diff
• Check the history using git log

Exercise 2

• Discuss in pairs what’s the difference between git diff, git status and git log

Exercise 3

• Add a new folder called data
• Add a file called mydata.tsv
• Save your changes

History summary

Now that we have a larger story on our project a good summary is

git log --oneline

Thing 2. Git Let’s you travel in time

git checkout [hash] filename
git status

Exercise 4

• Save your changes

Note: Make sure to always indicate the name of the file to checkout, or you might find yourself into a detached HEAD state. After checking your files you can recover by typing git checkout master

Ignoring things

Exercise 5

• Add a new folder called img
• Add a file called myplot.png
• Save your changes

There are some things like visual images that result from running your code and you should not need to save them, because you can generate them again.

• Use .gitignore to add the files to be ignored
• Before finishing this part make sure you check there is nothing to commit and your repo is all up to date.

Next: Game