{"id":231158,"date":"2020-11-12T08:00:46","date_gmt":"2020-11-12T16:00:46","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=231158"},"modified":"2020-12-08T12:03:09","modified_gmt":"2020-12-08T20:03:09","slug":"announcing-the-release-of-the-git-experience-in-visual-studio","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/announcing-the-release-of-the-git-experience-in-visual-studio\/","title":{"rendered":"Announcing the Release of the Git Experience in Visual Studio"},"content":{"rendered":"

We\u2019re excited to announce that our new Git tooling is now the default source control experience in Visual Studio 2019, beginning with version 16.8<\/a>. We’ve been working on this experience over the last year, iterating based on your feedback<\/a> to build out key features, enhance performance, and fine tune quality. Above all, we\u2019ve focused on improving discoverability for your common workflows and simplifying navigation to reduce context-switching. Regardless of whether you are part of a large team or working on a personal project, whether you are an experienced developer or just starting out, we strongly believe the new Git experience in Visual Studio 2019<\/a> will have something for you. Here’s seven reasons why we think you should try it out.<\/span><\/p>\n

Download Visual Studio<\/a><\/div><\/span><\/p>\n

\"Git<\/a><\/p>\n

Git Productivity in Visual Studio 2019<\/em><\/span><\/p>\n

Redesigned Git repository creation<\/h3>\n

To get started with Git, Visual Studio lets you add your local code to Git and GitHub with a single click. The Create a Git repository<\/strong> dialog contains the new integrated GitHub sign-in flow<\/a>, similar to what we offer for Microsoft accounts. Here, you can set the repository to be publicly visible or switch it to private. That makes it securely accessible to only you and any designated collaborators. In addition to GitHub, you can also push your code to an existing remote repository. This can be one you\u2019ve already created on Azure DevOps or any other provider. And finally, you can choose to create a local-only Git repository if you are not ready to push to a remote host.<\/span><\/p>\n

\"Image<\/a><\/p>\n

Create Repository dialog<\/em><\/p>\n

Accessible top level Git menu<\/h3>\n

You can now access your favorite Git features using the top level Git menu. It’s at easy reach through the Alt+G keyboard shortcut. This menu also has the Local Repositories submenu. By expanding it, you can easily switch between local Git repositories you have previously opened in Visual Studio.<\/span><\/p>\n

\"Image<\/a><\/p>\n

Git menu with Local Repositories list<\/em><\/p>\n

View files in Solution Explorer<\/h3>\n

After you’ve opened or cloned a Git repository, Visual Studio helps you get straight to your code. Solution Explorer loads the root of the repository and scans the directory for any View files. Instead of having to search for your .sln file to open it, Visual Studio detects and loads the solution automatically. If your repository has more than one .sln file, then Solution Explorer shows you the list of available views to choose from. Subsequently, you can toggle between the currently open Solution (view) and the list of Views by using the Switch Views button in the Solution Explorer Toolbar.<\/span><\/p>\n

\"Image<\/a><\/p>\n

Switch Views in Solution Explorer<\/em><\/p>\n

Streamlined inner loop Git Changes window<\/h3>\n

The new Git Changes window is designed to provide quick access to commonly used Git operations that you need while you are coding. You can create new branches, stash, stage, amend, and commit changes, all from the same place without switching pages or losing context. Moving to the top of the window, you’ll see handy fetch, pull, and push buttons. They allow you to sync commits and tags with your remotes (that’s right, multiple remotes!). The Git Changes window also has an indicator displaying the number of outgoing and incoming commits. This indicator functions as a link to take users to the Git Repository window. From there, you can view a summary of your outgoing and incoming commits before you sync.<\/span><\/p>\n

\"Image<\/a><\/p>\n

Staged Changes and Stashes in the Git Changes Window<\/em><\/p>\n

Full screen Git Repository window<\/h3>\n

If you like browsing and managing your repository, you no longer need to leave Visual Studio. The new Git experience comes with a rich Git Repository window that makes it easy to visualize the entire history of your repository. You can right click on a branch to perform operations like merge, rebase, reset, and cherry pick. Moreover, the Repository window is accessible through the Git menu, the View menu, and the status bar.<\/span><\/p>\n

\"Image<\/a><\/p>\n

Branch History in the Git Repository Window<\/em><\/p>\n

Enhanced merge conflict resolution<\/h3>\n

If you run into a merge conflict, Visual Studio now guides you through the process of resolving it. The Git Changes tool window clearly lists unmerged changes. Also, it displays a status message specifying that conflict resolution is in progress. Further, a gold info bar in the conflicting file prompts you to open the Merge Editor. Once you’re there, the three-way Merge Editor takes you through each conflict in the file. In other words, it allows you to compare lines and even individual word-level differences. Moreover, you can accept all current or incoming changes at the file level with a single click.<\/span><\/p>\n

\"Image<\/a><\/p>\n

Merge Conflict Resolution with the Merge Editor<\/em><\/p>\n

Customizable experience<\/h3>\n

We want you to be able to personalize your Git experience. To change any of your preferences at the repository level or the global level, go to Git \u2013 Settings <\/em>in the menu bar. This will take you to the consolidated Tools \u2013 Options<\/em> pane for Source Control.<\/span><\/p>\n

\"Image<\/a><\/p>\n

Git Settings in Tools – Options dialog<\/em><\/p>\n

However, if these features aren’t working out for you, it’s possible to revert back to the full Team Explorer experience. Go to Tools \u2013 Options \u2013 Environment – Preview Features <\/em>and toggle the New Git user experience<\/strong> checkbox. Please let us know<\/a> why!<\/span><\/p>\n

\"Image<\/a><\/p>\n

New Git user experience Preview Feature flag<\/em><\/p>\n

This is just the beginning<\/h3>\n

To summarize, from the new Git menu, you can clone, create, or open repositories. You can use the integrated Git tool windows to commit and push changes to your code, manage branches, sync your remote repositories, and resolve merge conflicts. Find the full list of capabilities in the Release Notes<\/a>. Learn how to use the features in our documentation<\/a>. Most importantly, join the conversation on Developer Community<\/a> to weigh in on what we’re building next. And please provide feedback<\/a> as we continue to enhance the Git experience in Visual Studio!<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

We\u2019re excited to announce that our new Git tooling is now the default source control experience in Visual Studio 2019, beginning with version 16.8. We’ve been working on this experience over the last year, iterating based on your feedback to build out key features, enhance performance, and fine tune quality. Above all, we\u2019ve focused on […]<\/p>\n","protected":false},"author":3029,"featured_media":231171,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[155],"tags":[431,6758,4381],"class_list":["post-231158","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-visual-studio","tag-git","tag-git-integration","tag-github"],"acf":[],"blog_post_summary":"

We\u2019re excited to announce that our new Git tooling is now the default source control experience in Visual Studio 2019, beginning with version 16.8. We’ve been working on this experience over the last year, iterating based on your feedback to build out key features, enhance performance, and fine tune quality. Above all, we\u2019ve focused on […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/231158","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/3029"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=231158"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/231158\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/231171"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=231158"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=231158"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=231158"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}