This very useful guide to Git commands comes to us from Premier Developer consultant Crystal Tenn<\/a>.<\/p>\n
\n
| \n Project\/Directory Setup Commands<\/b><\/p>\n<\/td>\n | \n Use\/Explanation<\/b><\/p>\n<\/td>\n<\/tr>\n git init<\/b><\/font><\/p>\n<\/td>\n New repository from current directory<\/p>\n<\/td>\n<\/tr>\n git init <directory><\/font><\/p>\n<\/td>\n New repository to a specific directory<\/p>\n<\/td>\n<\/tr>\n git clone \/path\/to\/repository<\/font><\/p>\n<\/td>\n Connecting to an existing local repository<\/p>\n<\/td>\n<\/tr>\n git clone username@host:\/path\/to\/repository<\/font><\/p>\n<\/td>\n Connecting to an existing remote repository<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n You need initialize a local file directory to be a Git repository for a new project (your local file directory will be associated with a certain online repository). Initializing will create a .git folder in the directory and this is where Git will record different versions of the project and the .git folder will contain all of the metadata and changes to the project (rest of the project will not be altered while you are working).<\/i><\/p>\n <\/em> <\/p>\n Adding\/Staging\/Unstaging Files Commands<\/b><\/b><\/p>\n<\/td>\n Use\/Explanation<\/b><\/p>\n<\/td>\n<\/tr>\n git add filename.txt<\/font><\/p>\n<\/td>\n Stages a specific file to commit<\/p>\n<\/td>\n<\/tr>\n git add -A<\/font><\/p>\n<\/td>\n Stages all<\/p>\n<\/td>\n<\/tr>\n git add .<\/font><\/p>\n<\/td>\n Stages new and modified, without deleted. *This add command is most commonly used<\/i><\/b><\/p>\n<\/td>\n<\/tr>\n git add -u<\/font><\/p>\n<\/td>\n Stages modified and deleted, without new<\/p>\n<\/td>\n<\/tr>\n git add *<\/font><\/p>\n<\/td>\n Stages all files in current directory except files whose name begin with a dot. Wildcard interpreted as part of git.<\/p>\n<\/td>\n<\/tr>\n git reset — filename.txt<\/font><\/p>\n<\/td>\n Unstages a file by name, the changes are still there that you made but it will not be committed until you add it back<\/p>\n<\/td>\n<\/tr>\n git reset<\/font><\/p>\n<\/td>\n Unstages all files (again changes are still there and now nothing is committed until you add it in)<\/p>\n<\/td>\n<\/tr>\n git status<\/font><\/p>\n<\/td>\n Checking file status (see which files are staged\/unstaged for the commit)<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Staging and unstaging do not affect the changes of the files or delete any files, they are for adding\/removing files to track for a commit or stash. You push your commits to make a change. In Git, you stage(add) the files you want to commit and unstage (reset) files you do not want to commit. Note \u2018–\u2019 in a command specifies we are talking about a file, not a branch (in case some file names are the same as a branch name).<\/i> <\/p>\n <\/em> <\/p>\n <\/i> <\/p>\n <\/i> <\/p>\n Commit\/Reset Commands<\/b><\/p>\n<\/td>\n Use\/Explanation<\/b><\/p>\n<\/td>\n<\/tr>\n git commit -m \u201cYour message here to describe what you are committing to your branch.\u201d<\/font><\/p>\n<\/td>\n Commit changes with a message<\/p>\n<\/td>\n<\/tr>\n git checkout <file><\/font><\/p>\n<\/td>\n Abandon\/Undo changes to one file<\/p>\n<\/td>\n<\/tr>\n git reset –hard HEAD~1<\/font><\/p>\n<\/td>\n Removing the most recent one commit (HEAD~1 means the commit before the head)<\/p>\n<\/td>\n<\/tr>\n git log<\/font><\/p>\n<\/td>\n Find a commit id<\/p>\n<\/td>\n<\/tr>\n git reset –hard <sha1-commit-id><\/font><\/p>\n<\/td>\n Removing a very specific commit id<\/p>\n<\/td>\n<\/tr>\n git reset –hard<\/font><\/p>\n<\/td>\n Removing all commits\/changes and reset back to original branch pulled<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Committing is not permanent, do not be afraid to commit. You don\u2019t have to push your commit. You can roll back this commit easily if you want to erase all of it and go back to the original code in the branch. You must commit or stash everything before you can change branches, pull new commits in, etc. (see final table for stashing info).<\/i><\/p>\n <\/em> <\/p>\n Push\/Pull Commands<\/b><\/p>\n<\/td>\n Use\/Explanation<\/b><\/b><\/p>\n<\/td>\n<\/tr>\n git push<\/font><\/p>\n<\/td>\n Pushing changes from current branch to the same current branch<\/p>\n<\/td>\n<\/tr>\n git push originally-cloned-branch new-branch<\/font><\/p>\n<\/td>\n Pushing changes from an originally cloned branch to a new branch<\/p>\n<\/td>\n<\/tr>\n git fetch<\/font><\/p>\n<\/td>\n Fetching commits and remote branch changes, does not put new changes into your code until you pull though<\/p>\n<\/td>\n<\/tr>\n git pull<\/font><\/p>\n<\/td>\n Pulls all the latest commits to your current branch from the server<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n You must run a <\/i>git fetch<\/i><\/b> to see new commits or any new branches added to your repository. Git pull<\/b> does a git fetch + git merge<\/b>. You can git fetch<\/b> anytime to update remote tracking branches or see any latest commits from others. If you already pushed a commit and need to revert it, you can do a force push to get rid of it but honestly it is safer for you to create a new branch and fix your changes as others are working in the same code (pushing is a little permanent, make sure you test everything out before you push your changes to the server where other developers will see your work).<\/i> <\/p>\n <\/em> <\/p>\n <\/i> <\/p>\n <\/i> <\/p>\n Switching\/Creating Branches<\/b><\/p>\n<\/td>\n Use\/Explanation<\/b><\/p>\n<\/td>\n<\/tr>\n git checkout -b my-new-branch-name<\/font><\/p>\n<\/td>\n Create a new branch based on your current branch, and switch to the new branch. Note the -b means that you need to create a new branch<\/i><\/p>\n<\/td>\n<\/tr>\n git checkout -b new-branch existing-branch<\/font><\/p>\n<\/td>\n Create a new branch based on a specific branch<\/p>\n<\/td>\n<\/tr>\n git checkout existing-branch-name<\/font><\/p>\n<\/td>\n Switching to another existing branch<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Make sure you commit or stash your changes before trying to change branches. Note: you are able to swap between different branches with one code same base\u2014all of the changes that appear are applied based on the contents of the .git folder on top of the original files. <\/i> <\/p>\n <\/em> <\/p>\n <\/i> <\/p>\n <\/i> <\/p>\n Merging Branches Commands<\/b><\/p>\n<\/td>\n Use\/Explanation<\/b><\/p>\n<\/td>\n<\/tr>\n git merge branchname<\/font><\/p>\n<\/td>\n Merges branchname<\/i> into your current branch. Make sure to pull latest into both your current branch and the branch to merge in<\/p>\n<\/td>\n<\/tr>\n git reset –merge .<\/font><\/p>\n<\/td>\n Abandon a merge with merge conflicts, goes back to state you were in before you attempted to merge. Can use this command if Git v1.6.1+<\/p>\n<\/td>\n<\/tr>\n git reset –hard HEAD<\/font><\/p>\n<\/td>\n If Git version is less than 1.6.1 then use this to abandon a merge<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n You merge one branch into another one, for example if you are working in a feature branch and want to put your work into develop.. or if you want to merge stable develop changes into QA. Careful with merge conflicts and to test after fixing all of them before committing and finally pushing to the server.<\/i><\/p>\n <\/em> <\/p>\n Dealing with Stashes Commands<\/b><\/p>\n<\/td>\n Use\/Explanation<\/b><\/p>\n<\/td>\n<\/tr>\n git stash<\/font><\/p>\n<\/td>\n Stash all tracked files without a message\/description to index 0<\/p>\n<\/td>\n<\/tr>\n git stash save \u201cmy description here\u201d<\/font><\/p>\n<\/td>\n Stash all tracked files that have not yet been committed<\/p>\n<\/td>\n<\/tr>\n git stash save -u \u201cmy description here\u201d<\/font><\/p>\n<\/td>\n Stash all files that have not yet been committed including<\/i> untracked files<\/p>\n<\/td>\n<\/tr>\n git stash pop<\/font> <\/p>\n -or- <\/font> <\/p>\n git stash apply<\/font><\/p>\n<\/td>\n All changes to stashed files will be applied to the current workspace (unstashing). You can reapply to same branch or apply changes to a new branch. By default gets stash@{0}. Important: <\/u><\/b>git stash pop throws away the stash after applying it, whereas git stash apply leaves it in the stash list for possible later reuse.<\/b><\/p>\n<\/td>\n<\/tr>\n git stash pop stash@{2} Specifies which index to apply\/unstash to your current workspace<\/p>\n<\/td>\n<\/tr>\n git stash list<\/font><\/p>\n<\/td>\n List the current stashes, you can see the index of each one to delete a certain one<\/p>\n<\/td>\n<\/tr>\n git stash clear<\/font> <\/p>\n<\/td>\n Clear\/Delete all the current stashes<\/p>\n<\/td>\n<\/tr>\n git stash drop stash@{0}<\/font><\/p>\n<\/td>\n Replace {0} with the index of the stash you want to drop<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Use git add\/reset to determine which files you want to stash. You can stash changes as a \u201csave-state\u201d so you can do work in another branch, all changes will be saved in your local Git repo and nothing from the stash will go to the server. You can easily unstash your changes onto the same or another branch. You can apply one stash to multiple other branches. Sometimes you may make a feature branch and make a lot of foundational domain changes.. then suddenly you realize another developer needs your changes to work. You can stash your changes and unstash them on top of the other branch so you are both working in the same branch with shared foundational code. New git stashes by default are always created to stash@{0}, and older ones\u2019 will have the index pushed to higher index numbers.<\/i><\/p>\n","protected":false},"excerpt":{"rendered":" This very useful guide to Git commands comes to us from Premier Developer consultant Crystal Tenn. Git command line is extremely useful for managing your resources \u2013 it is the only way to utilize all Git commands possible as most GUI\u2019s only have a set of available commands. Although many guides exist to explain Git […]<\/p>\n","protected":false},"author":581,"featured_media":37840,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[76,43],"class_list":["post-10166","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-permierdev","tag-crystal-tenn","tag-git"],"acf":[],"blog_post_summary":" This very useful guide to Git commands comes to us from Premier Developer consultant Crystal Tenn. Git command line is extremely useful for managing your resources \u2013 it is the only way to utilize all Git commands possible as most GUI\u2019s only have a set of available commands. Although many guides exist to explain Git […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/posts\/10166","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/users\/581"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/comments?post=10166"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/posts\/10166\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/media\/37840"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/media?parent=10166"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/categories?post=10166"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/tags?post=10166"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}} |