Muokkaa

Jaa

Git settings and preferences in Visual Studio

  • Artikkeli

In Visual Studio, you can configure and view common Git settings and preferences, such as your name and email address, your preferred diff and merge tools, and more. These settings and preferences can be viewed and configured in the Options dialog box on either the Git Global Settings page (applies to all your repositories) or the Git Repository Settings page (applies to the current repository).

You can configure two types of settings:

  • Git settings - The settings in this section correspond to Git settings that are saved in Git configuration files. These settings can be viewed and modified in Visual Studio, but are managed by Git configuration files.
  • Visual Studio settings - The settings in this section configure Git-related settings and preferences that are managed by Visual Studio.

How to configure settings

  1. To configure Git settings in Visual Studio, choose Settings from the top-level Git menu.

    The Git menu with a callout to the Settings command.

  2. Choose Git Global Settings or Git Repository Settings to view and configure global-level or repository-level settings.

    The navigation pane in the Options dialog box with a callout to Git settings.

  3. You can configure several common Git settings, as described in the following sections of this article. After configuring your desired settings, select OK to save the updated settings.

    The display area of the Options dialog box with a callout to the OK button.

Git settings

You can also configure and check some of the most common Git configuration settings. You can view and modify the following settings in Visual Studio, even though they are managed by Git configuration files.

Note

Git settings configured in Visual Studio's Global Settings correspond to settings in Git's user-specific configuration file, and the settings in Repository Settings correspond to settings in the repository-specific configuration file. For more information about Git configuration, see the Pro Git chapter on customizing Git, the git-config documentation, and the Pro Git reference on configuration files. To configure Git settings not exposed in Visual Studio, use the git config command to write a value to your configuration files: git config [--local|--global|--system] section.key value.

Name and email

The name and email that you provide will be used as the committer information for any commit you make. This setting is available at both global and repository scopes, and corresponds to the git config user.name and user.email settings.

  1. From the Git menu, go to Settings. To set your user name and email at the global level, go to Git Global Settings; to set your user name and email at the repository level, go to Git Repository Settings.

  2. Provide your user name and email, then choose OK to save.

    Git Global settings pane in Options dialog box with a callout to username an email.

Prune remote branches during fetch

Pruning removes remote-tracking branches that no longer exist on the remote and helps you keep your branches list clean and up to date. This setting is available at both global and repository scopes, and corresponds to the git config fetch.prune setting.

We recommend setting this option to True at the global level. Valid settings are, as follows:

  • True (recommended)
  • False
  • Unset (default)

Here's how to change the settings:

  1. From the Git menu, go to Settings. Go to Git Global Settings to configure this option at the global level; go to Git Repository Settings to configure this option at the repo level.

  2. Set Prune remote branches during fetch to True (recommended). Select Ok to save.

    Screenshot that shows 'Prune remote branches during fetch' highlighted and with 'True' selected from the drop-down.

Rebase local branch when pulling

Rebasing sets aside the changes made by commits in the current branch that are not in the upstream branch, resets the current branch to the upstream branch, then applies the changes that were set aside. This setting is available at both global and repository scopes, and corresponds to the git config pull.rebase setting. Valid settings are, as follows:

  • True: Rebase current branch on top of upstream branch after fetch.

  • False: Merge the current branch into the upstream branch.

  • Unset (default): Unless specified in other configuration files, merge the current branch into the upstream branch.

  • Interactive: Rebase in interactive mode.

  • Merges: Rebase without flattening locally created merge commits.

    Note

    In Visual Studio 2022 version 17.2, we changed the "Preserve" setting to "Merges" to match a recent update from Git. So, if you're using an earlier version of Visual Studio with Git tooling, your user interface might say "Preserve" instead of "Merges". The functionality remains the same, however.

Here's how to change the settings:

  1. From the Git menu, go to Settings. Go to Git Global Settings to configure this option at the global level; go to Git Repository Settings to configure this option at the repo level.

  2. Set Rebase local branch when pulling to the desired setting, and select OK to save.

    Screenshot that shows 'Rebase local branch when pulling' highlighted and 'Merges' selected from the drop-down.

It's not possible to configure pull.rebase to Interactive in Visual Studio. Visual Studio doesn't have interactive rebase support. To configure pull.rebase to use interactive mode, use the command line.

Cryptographic network provider

Cryptographic network provider is a Git configuration setting at global scope that configures which TLS/SSL backend to use at runtime, and corresponds to the git config http.sslBackend setting. The values are, as follows:

  • OpenSSL: Use OpenSSL for TLS and SSL protocols.
  • Secure Channel: Use Secure Channel (schannel) for TLS and SSL protocols. Schannel is the native Windows solution, accessing the Windows Credential Store, thereby allowing for enterprise-wide management of certificates.
  • Unset (default): If this setting is unset, OpenSSL is the default.

Here's how to change the settings:

  1. From the Git menu, go to Settings. Go to Git Global Settings to configure this setting.

  2. Set Cryptographic network provider to the desired value, and select OK to save.

    Screenshot that shows 'Cryptographic network provider' highlighted with 'OpenSSL' selected from the drop-down.

Credential helper

When Visual Studio performs a remote Git operation, the remote endpoint might reject the request because it requires credentials to be provided with the request. At that time, Git invokes a credential helper, which will return the credentials needed to perform the operation, and then will try the request again. The credential helper used corresponds to the git config credential.helper setting. It is available at the global scope with the following values:

Here's how to change the settings:

  1. From the Git menu, go to Settings. Go to Git Global Settings to configure this setting.

  2. Set Credential helper to the desired value, and select OK to save.

    Screenshot showing the credential helper setting in the Options dialog box.

Diff & merge tools

Git will show diffs and merge conflicts in your preferred tools. The settings in this section correspond to the git config diff.tool and merge.tool settings. You can configure Git to use Visual Studio as your merge or diff tool in Git Global Settings and Git Repository Settings by selecting Use Visual Studio. To configure other diff and merge tools, use git config with the diff.tool or merge.tool switch.

Screenshot that shows the section to set default Diff tool and Merge tool in the Options dialog box.

Git files

You can use the Git files section in the Git Repository Settings scope to view and edit the gitignore and gitattributes files for your repository.

Screenshot that shows the section to view and edit the Ignore and attributes files in your repository.

Remotes

You can use the Remotes pane under Git Repository Settings to configure the remotes for your repository. This setting corresponds to the git remote command and allows you to add, edit, or remove remotes.

Screenshot showing the Git Remotes pane in the Options dialog box.

Other settings

To view all of your other Git configuration settings, you can open and view the configuration files themselves, or you can run git config --list to display the settings.

Visual Studio settings

The following settings manage Git-related preferences in Visual Studio, and are managed by Visual Studio instead of Git configuration files. All of the settings in this section are configured in the Git Global Settings page.

Default location

Default location configures the default folder in which repositories are cloned.

Screenshot showing the default location field in the Options dialog box.

Close open solutions not under Git when opening a repository

By default, Visual Studio closes any open solution or folder when you switch to another repository. When it does so, it might also load the solution or folder of the new repository based on if you choose to Open folder in Solution Explorer when opening a Git repository and Automatically load the solution when opening a Git repository. This maintains the consistency between the open code and open repository. However, if your solution is not in the same folder root as your repository, you may want to keep the solution open when you switch to its repository. You can do that with this setting. The values are, as follows:

  • Yes: When a repository is opened, the currently open solution is always closed

  • No: When a repository is opened, Visual Studio performs a check as to whether the current solution is under Git. If it is not, then the solution remains open.

  • Always ask (default): When this is set, you can make a choice through a dialog box per repository open, whether you want to keep the current solution open or close it.

    Screenshot showing the close solution setting in the Options dialog box.

Enable download of author images from third-party sources

Enable download of author images from third-party sources is a Visual Studio-specific setting at global scope. When checked, author images are downloaded from the Gravatar image service, if available, and displayed in the commit and history views.

Screenshot showing checkbox to enable download of author images from third-party source in the Options dialog box.

Important

In order to provide author images in the Commit and History views, the tool creates an MD5 hash for the author email addresses stored in the active repository. This hash is then sent to Gravatar to find a matching hash value for users that have previously signed up for the service. If a match is found, the user image will be retrieved from the service and displayed in Visual Studio. Users that have not configured the service will return a randomly generated image. Note, email addresses are not recorded by Visual Studio, nor are they ever shared with Gravatar or any other third party.

Commit changes after merge by default

When Commit changes after merge by default is enabled, Git automatically creates a new commit when a branch is merged with the current branch.

Screenshot showing the checkbox to commit changes after merge by default in the Options dialog box.

  • When checked, git merge commands issued by Visual Studio are run with the --commit option.
  • When unchecked, git merge commands issued by Visual Studio are run with the --no-commit --no-ff options.

For more information on these options, see --commit and --no-commit and --no-ff.

Enable push --force-with-lease

When enabled, this setting allows you to push --force-with-lease from within Visual Studio. By default Enable push --force-with-lease is disabled.

Screenshot showing the checkbox to enable push force with lease in the Options dialog box.

For more information, see push --force-with-lease.

Open folder in Solution Explorer when opening a Git repository

When you use Visual Studio to open or switch to a Git repository, Visual Studio loads the Git content so that you can view changes, commits, branches, and manage your repository from within the IDE. In addition, Visual Studio will also load the code of the repository in Solution Explorer. Visual Studio will scan the repository folder for solutions, CMakeLists.txt, or any other view files that it recognizes and display them as a list in Solution Explorer. From there, you can select a solution to load or the folder to view the directory contents. When you turn off this checkbox, then Visual Studio will not open the repository folder in Solution Explorer. This will essentially allow you to open Visual Studio as a Git repository manager only. This setting is on by default.

Screenshot showing the checkbox to open folder when opening a Git repository in the Options dialog box.

Automatically load the solution when opening a Git repository

This setting is applicable only when the Open folder in Solution Explorer when opening a Git repository setting is turned on. When you open a Git repository in Visual Studio, and the subsequent folder scan detects there is only one solution present in your repository, then Visual Studio automatically loads that solution. If you turn off the setting, then the Solution Explorer will display the single solution present in the repository in the list of views. But it will not load the solution. By default, this setting is off.

Screenshot showing the checkbox to automatically load the solution when opening a Git repository in the Options dialog box.

Automatically check out branches with double-click or the Enter key

The Git Repository window has a list of branches displayed in a tree structure. Single selecting a branch will switch the commit history pane to display the commits for the selected branch. To check out a branch, you can right-click to open the context menu and select Checkout. If you turn on this setting, then double-clicking or pressing the Enter key will check out the branch and display its commits.

Screenshot showing the checkbox to check out branches with double-click or Enter key in the Options dialog box.

Related content

Important

If you have a suggestion for us, please let us know! We appreciate the opportunity to engage with you on design decisions via the Developer Community portal.