Scope
I have used many SCM in the past. VSS, SVN, TFS, ClearCase, Mercurial etc... There are so many of them yet they are so similar, so that they are not even worthy for a spot in a resume.
However, git was a little more challenging to me as their structures and architectures are different. I have now used git for just over a year now, and put the followings together that covered what I believe is a good starting point to learn git commands.
However, git was a little more challenging to me as their structures and architectures are different. I have now used git for just over a year now, and put the followings together that covered what I believe is a good starting point to learn git commands.
Technical
Config
I use posh-git and found the default dark red color was a bit hard to read against a dark background color in Windows console. I changed them to yellow and magenta by updating the ~/.git/config.
[color] ui = true [color "status"] changed = magenta bold untracked = yellow bold
Settings
# Change a global setting $ git config --global --edit # Change editor to notepad globally $ git config --global core.editor notepad # Setup git diff / merge tool globally # for example, if we are using p4merge as a diff / merge tool. $ git config --global diff.tool p4merge $ git config --global merge.tool p4merge # Git merge generates unwanted .orig file $ git config --global mergetool.keepBackup false
Basic Changes
# Check pending check-in status $ git status # Get latest files $ git pull # Change branch $ git checkout <branchName> # Add files for pending check in $ git add <filename> # Undo a git add $ git reset <filename> # Delete files for pending check in $ git rm <filename> # Undo pending delete files $ git reset head <filename> # Amend last commit $ git commit --amend # Undo commit # This will reset the the branch to a previous commit $ git reset HEAD~ # Hard reset is a potentially dangerous command # Changes are destructive and may not be recovered $ git reset --hard <commit-id> # a force push will force the origin to point to the same commit as local $ git push origin HEAD --force # Discard changes in working directory $ git checkout <filename> # Discard untracked files in working directory # Double check what to delete $ git clean -f -n # The actual deleting $ git clean -f # Discard untracked folders in working directory $ git clean -df
Stash
It is similar to shelve in TFS.
# All unstaged and staged dirty files will be "stashed", # and the working directory will be cleaned. $ git stash # shows the list of stash $ git stash list # shows content of stash $ git stash show -p # retrieve then remove changes from the stash $ git stash pop # apply changes (and not removing) from the stash $ git stash apply # remove changes from the stash $ git stash drop # remove all stash history $ git stash clear
Branch
# Delete a local branch $ git branch -d <branchName> # Delete a remote branch $ git push origin --delete <branchName> # Rename current branch $ git branch -m <newname>
Merge
# Merge a branch from source to destination $ git checkout destination-branch $ git merge source-branch # Resolve a merge conflict $ git mergetool # Resolve merge conflict with theirs or ours preference during a conflicted state. # Take their changes $ git checkout --theirs * $ git add * # Take our changes $ git checkout --ours * $ git add *
Tag
There are 2 types of tags in Git - What is the difference between an annotated and unannotated tag?
# listing tags $ git tag # add tag $ git tag -a <tagName> -m "A message for tagging" # push local tags to remote $ git push origin --tags # branch out from a tag $ git checkout -b <newBranchName> <fromTag>
Rebase
# Rebase branch from parent branch $ git rebase <parentBranch> # Conflict during rebase $ git rebase --[abort|skip|continue]
Fork and Submodule
# Add a remote repo to current repo as a subfolder $ git submodule add <gitRepo> # Get latest in submodule $ git submodule update
No comments:
Post a Comment