| layout | title | subtitle | minutes |
|---|---|---|---|
page |
Version Control with Git |
Setting Up Git |
10 |
- Explain which initialization and configuration steps are required once per machine, and which are required once per repository.
We'll start by exploring how version control can be used to keep track of what one person did and when. Even if you aren't collaborating with other people, version control is much better for this than this:
"Piled Higher and Deeper" by Jorge Cham, http://www.phdcomics.com
The first time we use Git on a new machine, we need to configure a few things. Here's how Dracula sets up his new laptop:
$ git config --global user.name "Vlad Dracula"
$ git config --global user.email "[email protected]"
$ git config --global color.ui "auto"
$ git config --global core.editor "nano"
(Please use your own name and email address instead of Dracula's,
and please make sure you choose an editor that's actually on your system,
such as notepad on Windows.)
Git commands are written git verb,
where verb is what we actually want it to do.
In this case,
we're telling Git:
- our name and email address,
- to colorize output,
- what our favorite text editor is, and
- that we want to use these settings globally (i.e., for every project),
The four commands above only need to be run once:
the flag --global tells Git to use the settings for every project on this machine.
In some networks you need to use a proxy. If this is the case you may also need to tell Git about the proxy:
$ git config --global http.proxy proxy-url $ git config --global https.proxy proxy-urlTo disable the proxy, use
$ git config --global --unset http.proxy $ git config --global --unset https.proxy