Page tree
Skip to end of metadata
Go to start of metadata

It is recommended to learn a little about the theory behind Git before diving in. Codecademy has a free course. This cheat sheet is also helpful.



Refer to the official documentation.

GUI Clients


Auditing configuration

It helps to first audit your Git configuration to find any existing configuration files.

To view all configured settings by configuration file, run:

$ git config --list --show-origin 

Keep in mind there may be multiple configuration files on your system. You might need admin/root access to edit some of them.

Typical paths for Git configuration files:

  • ~/.config/git/config
  • ~/.gitconfig

Setting a value from the command line

To set a global configuration value quickly on the command line, use:

$ git config --global value 

Note that you must use quotation marks for strings on command line

  • Set  to Firstname Lastname 
  • Set  to 
  • Set pull.rebase to true . This helps keep history linear during busy development times. Learn more:
  • Set credential.helper  to store --file=~/.config/git/credentials   (Path may vary on different systems)

Example Git Configuration File

	name = Rosie Robot
	email =
	rebase = true
	helper = store --file=/home/rosie/.config/git/credentials
[credential ""]
    username = rosie
[credential ""]
	username = rosie

Setting Credentials to Avoid Typing Password all the Time

Set the credential.helper = store --file=... property as shown in the example above and create an empty file at that location.

Fill out the entries as shown below. Not that you must use percent encoding for any reserved characters. Look at that Wikipedia link to find the right codes.

If you have trouble with this not working and SmartGit, Eclipse, IntelliJ, Git are still asking for the password all the time, check this file. The entries might have gotten deleted because the username didn't match the credential.username, user name and email were wrong, the password was wrong, or the server was down. Furthermore if authentication fails for any reason these entries may get deleted and you will have to re-add them.


Tips and Tricks

Line endings on Windows

We want to use LF on all files in our repositories to maintain multi-platform compatibility.

Setting core.autocrlf input should keep all files LF and converting them from CRLF on commit if necessary, but not the other way around.

Reverting a workspace to LF

If you need to change the line endings of a Windows workspace from CRLF to LF, set core.autocrlf = false and then run on all repos:

git add --renormalize .
git checkout -- .

# Or using vcstool:
vcs custom -n -w 1 repos --args add --renormalize .
vcs custom -n -w 1 repos --args checkout -- .

You may need to unstage and discard local changes after doing this.

Committing filtered diffs between branches

Say you want to make your working tree contain the changes "to get to" the state of another commit. To accomplish this might be counter intuitive:

  • Hard reset to the commit or branch "to get to"
  • Mixed reset to your current branch
  • Checkout your current branch

Your working tree should now have changes that would get you to the exact state of the other commit, but the advantage is that you can filter through the changes and selectively commit them.

Large File Storage

Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like or Bitbucket Server.

To use it:


Finding Unmerged Branches

git branch -r --no-merged origin/develop


See More

  • No labels