The command is also available in the top-level Git menu, which allows Sync to have its own keyboard shortcut (Alt+G+S) for quick access. The added benefit of the Sync command is that it synchronizes your local branch with the remote in one click. Sync is short for Synchronize and is a combination of a Pull and then a Push. Outgoing / Incoming commits dropdown with Sync functionality When you click this button, you’ll see a new flyout with commands to Fetch, Pull, Push, and Sync (which we brought back by popular demand)! And soon, it’ll also show you the number of unpulled commits. This button displays the number of commits that haven’t been pushed to the remote. It provides a shortcut to open the Git Changes window.īutton to open Git Changes window Sync commitsĪnd the final button in the status bar shows your Git remote operations. The Changes button in the status bar shows the number of changed files that haven’t been committed yet.
#VISUAL STUDIO COMPARE FOLDERS CODE#
Preference to load code when opening repositories Pending changes If you want to open code files, then you can load the solution or folder later. This will make Visual Studio essentially a Git-only tool. Our first step to help here is to provide an option to open only a repository, and not any code files with it. For example, you might want to change branches or pull commits before you open a solution or folder. We’ve also gotten feedback that some developers prefer to use Visual Studio as a Git tool before they start coding. Preference to choose whether to close solutions when switching repositories Now, you can customize that behavior by toggling the new preference in Git > Settings.
If so, you’ll want to keep the solution open when you open a repository even though they’re in different folders. But we’ve seen situations where your solution might be outside of your Git repository. For example, if you switch to a different repository, then the open solution will close and the new solution will open. Normally, Visual Studio will maintain consistency between the open repository and the open solution so that they are never out of sync. List of solutions for the repository in Solution Explorer Customize repository behavior If you have multiple solutions in the repository, then Solution Explorer displays the list of solutions. Info bar to establish initial connection to Azure DevOps project Solution listīy default, whenever you open a repository, Visual Studio loads the associated solution/folder in Solution Explorer. And after the initial connection is established, Visual Studio remembers it so that it auto-connects the next time you open the repository. Doing so will allow you to access Work Items and Builds for the project. If the remote of the repository is hosted on Azure DevOps, you’ll get a prompt in Git Changes to connect to the Azure DevOps Project. Whenever you open a version-controlled folder or solution for the first time in Visual Studio, you’ll see the associated Git repository appear in your local repositories list along with any of its nested sub-repositories. Repository picker in the status bar Opening repositories Soon, you’ll be able to remove items from this list as well. You can see all of your local repositories sorted in alphabetical order, and you can filter the list, too. The repository button in the status bar now has the first iteration of a repository picker when you select it.
#VISUAL STUDIO COMPARE FOLDERS WINDOWS#
The context menu gives you actions to perform on a branch, regardless of which tool windows you have visible.īranch picker in the status bar Repository picker With this visual overhaul, you’ll have access to search branches and can view both local and remote branches. Branch pickerīeginning with the rightmost button, the well-known branch picker now looks similar to the branch drop-down in the Git Changes window. And we started to expand the functionality there. The section of the status bar at the bottom right of the IDE window has a tray of always accessible Git commands. The first set of changes is to the status bar. In 16.10, we’ve built new functionality that addresses gaps around discoverability, switching repositories, navigation, and more! In the last iteration, 16.9, we listened to your feedback and focused on fixing issues after the first public release of the Git experience.
0 kommentar(er)
