Difference between revisions of "Git command summary"

From Jens' Hjørne
Jump to navigation Jump to search
m
m
Line 1: Line 1:
 
==Configuration==
 
==Configuration==
−
Editing the global configuration:
+
Editing the local configuration (.git/config):
 +
$'''git config --edit'''
 +
 
 +
Editing the global configuration (~/.gitconfig):
 
  $'''git config --global --edit'''
 
  $'''git config --global --edit'''
 +
 +
Editing the system configuration ($(prefix)/etc/gitconfig):
 +
$'''git config --system --edit'''
  
 
Retrieve the locations (and name value pairs) of all git configuration files:
 
Retrieve the locations (and name value pairs) of all git configuration files:
Line 9: Line 15:
 
  $'''git config --list --system --show-origin'''
 
  $'''git config --list --system --show-origin'''
  
−
Retrieve the locations of all git configuration files:
+
Retrieve the locations of all git configuration files (it fails when there's a space in the file name):
 
  $'''git config --list --show-origin | awk '{print $1}' | uniq'''
 
  $'''git config --list --show-origin | awk '{print $1}' | uniq'''
  

Revision as of 14:27, 6 June 2017

Configuration

Editing the local configuration (.git/config):

$git config --edit

Editing the global configuration (~/.gitconfig):

$git config --global --edit

Editing the system configuration ($(prefix)/etc/gitconfig):

$git config --system --edit

Retrieve the locations (and name value pairs) of all git configuration files:

$git config --list --show-origin

Retrieve the location (and name value pairs) of the system git configuration file:

$git config --list --system --show-origin

Retrieve the locations of all git configuration files (it fails when there's a space in the file name):

$git config --list --show-origin | awk '{print $1}' | uniq

Set git up to use Sublime Text

Create a batch/bash script that executes Sublime like this:

$subl -new-window -wait parameters to script
  • -new-window makes Sublime open a new window for the edit.
  • -wait makes sure that Sublime has focus until you close the file, this means that the script will start Sublime and wait, in stead of starting Sublime as a sub-process and then go on.

Make git call the script file (I assume it's not in your path):

$git config --global core.editor script incl. path

Cloning

Clone a GitHub project:

$git clone URL from GitHub

This will create a directory for the cloned code in the current directory, and pull all the code from GitHub and into the directory.

Branching

List branches:

$git branch

Creating a branch:

$git branch branch-name

Switch branch:

$git checkout branch-name

Deleting a branch:

$git branch -d branch-name

Remove changes

Remove changes to the current branch:

$git reset --hard HEAD

Staging

This should be done for both new and changed files

$git add file-name

Please also see the section on Committing for an alternate method when no new files have been added.

Merging

If changes has been made to the master which you want to merge into your branch:

$git merge master

Committing

Commit changes:

$git commit -m "Commit message goes here."

If you only have changed files and no new added files, you can do this without adding the changed files:

$git commit -am "Commit message goes here."

Push committed changes:

$git push

Diffing

To see a list of changes made to the files on disk:

$git diff

To see a list of changes made to the files on disk, ignoring differences in white spaces at the start and end of the line:

$git diff -w

To see a list of changes that have been staged:

$git diff --cached

Update changed code

To update code that has changed on the master branch, you need to 'stash' the changed code, pull the updated code and 'unstash' the stashed code. You may also have to switch branches in the process:

$git stash
$git checkout master
$git pull --rebase
$git checkout branch-you-came-from
$git stash apply