{"id":3223,"date":"2013-03-08T05:14:00","date_gmt":"2013-03-08T05:14:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2013\/03\/08\/use-the-git-command-prompt-to-supplement-visual-studio\/"},"modified":"2019-02-14T17:54:38","modified_gmt":"2019-02-15T01:54:38","slug":"use-the-git-command-prompt-to-supplement-visual-studio","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/use-the-git-command-prompt-to-supplement-visual-studio\/","title":{"rendered":"Use the Git command prompt to supplement Visual Studio"},"content":{"rendered":"

\/\/<\/p>\n

By: Andy Lewis<\/a> and Matthew Mitrik<\/a><\/p>\n

In Visual Studio Tools for Git we aim to offer the fundamental features you need to develop an app in a Git version-controlled codebase. We explain how to perform these tasks in previous posts such as Create, Connect, and Publish using Visual Studio with Git<\/a> and in our Git welcome portal content<\/a>.<\/p>\n

That said, there is a long tail of less-common tasks in software development work. If you can’t yet do what you want to do in VS, you might be able to do it from the command prompt. Also, many developers find the command prompt to be a handy and efficient way to perform repetitive tasks, either manually or with a script.<\/p>\n

Got the latest version of Visual Studio with Git? If not, click here.<\/a><\/p>\n

\n

To use the Visual Studio client tools you’ll need to install Visual Studio 2012<\/a>, apply Visual Studio 2012 Update 2<\/a>, and finally install Visual Studio Tools for Git<\/a>. If you want to use Team Foundation Service, you can sign up for free<\/a>.<\/p>\n<\/div>\n

Get set up to use the command prompt tools<\/h2>\n

Enable basic authentication for your TFS account<\/h2>\n

If your repo is hosted in Team Foundation Service (TFS), then you must enable basic authentication before you can use the command prompt to fetch, pull, push, clone, etc. You can set this up from your User Profile in TFS. Show me.<\/a><\/p>\n

\"\"<\/div>\n

Tip:<\/strong> To make using the command prompt less tedious (for example, to avoid having to enter your credentials every time you push), you might want to also install Windows Credential Store for Git<\/a> on your dev machine.<\/p>\n

Get the command prompt tools<\/h2>\n

If you have not already installed some command-prompt tools, you can get some quickly from Visual Studio. (One way you can tell that you don’t have the tools is if you try to enter a git command and get the ‘git’ is not recognized as an internal or external command…<\/span> message.) Go to the Settings <\/strong>page and click Install 3rd-party tools<\/strong>. Show me.<\/a><\/p>\n

\"\"<\/div>\n

Tip: <\/strong>The install process drops a Git Bash <\/strong>icon on your desktop. You can delete this icon; we don’t believe this entry point leads to the best experience. And anyway, you can still get to it from Windows Start if for some reason you need it later.<\/p>\n

Open the Git command prompt window<\/h2>\n

You can open the command prompt from the Actions menu on the Changes, Commits, and Branches pages. You can also open it from the Connect <\/strong>page: Right-click your local repo, and then click Open Command Prompt<\/strong>. Show me.<\/a><\/p>\n

\"\"<\/div>\n

Work from the command prompt<\/h2>\n

We hope you find the following table to be a useful if not complete guide to some of the more common tasks. You can find more command-prompt reference information here: http:\/\/git-scm.com\/docs<\/a>.<\/p>\n

Caution:<\/strong> If you are not an experienced Git user, use the command-prompt carefully. Make sure to research the command thoroughly before you use it.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Task<\/td>\nVisual Studio<\/td>\nCommand Prompt<\/td>\n<\/tr>\n<\/thead>\n
\n

Create a local repository<\/p>\n<\/td>\n

Yes<\/a><\/td>\ngit-init<\/a><\/td>\n<\/tr>\n
\n

Copy a remote repository to your dev machine<\/p>\n<\/td>\n

Yes<\/a><\/td>\ngit-clone<\/a><\/td>\n<\/tr>\n
\n

Fetch and pull changes from a remote repository<\/p>\n<\/td>\n

Yes<\/a> (some conflicts can be resolved only at command prompt)<\/td>\ngit-fetch<\/a>, git-pull<\/a><\/td>\n<\/tr>\n
\n

Get information about a repository<\/p>\n<\/td>\n

You can if it is in a TFS team project (shown in bold text<\/a> and with hover info in Team Explorer)<\/td>\ngit-remote<\/a><\/td>\n<\/tr>\n
\n

Commit your changes<\/p>\n<\/td>\n

Yes<\/a><\/td>\ngit-commit<\/a><\/td>\n<\/tr>\n
\n

Amend your last commit. Some typical cases:<\/p>\n

No<\/td>\ngit-commit<\/a><\/td>\n<\/tr>\n
\n

Undo a committed change by applying the inverse of the commit. See rolling back changes with revert<\/a>.<\/p>\n<\/td>\n

No<\/td>\ngit-revert<\/a><\/td>\n<\/tr>\n
\n

Undo committed changes by returning your local repo to a prior commit and de-referencing the later commit.  See Undoing Things<\/a>, which warns, “…this is a dangerous command<\/strong>: any changes you made to that file are gone — you just copied another file over it. Don’t ever use this command unless you absolutely know that you don’t want the file.”<\/p>\n<\/td>\n

No<\/td>\ngit-reset<\/a><\/td>\n<\/tr>\n
\n

Branch and merge<\/p>\n<\/td>\n

Yes (some conflicts can be resolved only at command prompt). (We plan to post more info on branches. For now, see our announcement post<\/a>.)<\/td>\ngit-branch<\/a>, git-merge<\/a><\/td>\n<\/tr>\n
\n

Re-order history or combine commits. See Git Branching – Rebasing<\/a>.<\/p>\n<\/td>\n

No<\/td>\ngit-rebase<\/a><\/td>\n<\/tr>\n
\n

Push changes to a remote repository<\/p>\n<\/td>\n

Yes<\/a><\/td>\ngit-push<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<!–<\/p>\n

Use the Git command prompt to supplement Visual Studio<\/h2>\n

–><\/p>\n","protected":false},"excerpt":{"rendered":"

\/\/ By: Andy Lewis and Matthew Mitrik In Visual Studio Tools for Git we aim to offer the fundamental features you need to develop an app in a Git version-controlled codebase. We explain how to perform these tasks in previous posts such as Create, Connect, and Publish using Visual Studio with Git and in our […]<\/p>\n","protected":false},"author":91,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[253,1,225],"tags":[],"class_list":["post-3223","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure-devops-server","category-devops","category-git"],"acf":[],"blog_post_summary":"

\/\/ By: Andy Lewis and Matthew Mitrik In Visual Studio Tools for Git we aim to offer the fundamental features you need to develop an app in a Git version-controlled codebase. We explain how to perform these tasks in previous posts such as Create, Connect, and Publish using Visual Studio with Git and in our […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/3223","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/91"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=3223"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/3223\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/45953"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=3223"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=3223"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=3223"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}