Как отключить git в visual studio
У меня настроена политика SRP, поэтому как-то появилось предупреждение о заблокированном файле:
Access to C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\cmd\git.exe has been restricted by your Administrator by the default software restriction policy level.
Для контроля версий я использую GitHub Desktop, поэтому я захотел отключить встроенную в Visual Studio поддержку Git.
Вроде нашёл настройку здесь:
Tools ▶ Options… ▶ Source Control ▶ [ Plug-in Selection ] ▶ None
После этого нужно будет подтвердить свой выбор.
Для существующего проекта описанный выше способ не сработал, т.к. там уже использовался GithubDesktop. Данная утилита создала файлы для синхронизации через git.exe, их-то и перехватывала VS.
Отключение плагина контроля версий через консоль
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\Extensions\Community\MSSCCIHostActive.rgi_41972.3643236F_FC70_11D3_A536_0090278A1BB8.pkgdef
В папке с TeamFoundation нашлось ещё одно упоминание. Путь к файлу такой:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\TeamExplorer.pkgdef
В нём я встретил такую запись:
Благодаря этим строчкам мы узнали GUID плагинов, попробуем удалить его через Developer Command Prompt for VS 2019 :
1. Создаём текстовый файл devenv.pkgundef
2. Добавляем в него строчку с нашим GUID в фигурных скобках:
3. Копируем этот файл в папку:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE
4. Закрываем Visual Studio 2019
5. Запускаем с правами администратора Developer Command Prompt for VS 2019
6. В этой консоли переходим в папку с VS:
7. Выполняем обновление конфигурации:
При первом запуске Visual Studio плагин контроля версий не будет активен (будет выставлено значение None). Правда в правом нижнем углу редактора всё равно останется кнопочка «Add to Source Control». Если на неё нажать, всё подцепится заново.
Радикальный способ избавления от Git.exe
Необходимо добавить «.bak» (просто изменить расширение на другое) у следующих файлов:
« C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Microsoft.TeamFoundation.Git.Provider.dll »
« C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\VS SCC\VssProvider.dll »
И ещё один файл:
«C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\cmd\git.exe»
В ней будет коротко рассмотрено что это за вещи, зачем нужны, и простой способ работы – из среды Visual Studio. То есть Bash или GitHub клиент использоваться не будут.
Внимание:
На Хабре уже есть похожая статья – [вот она]. В своей публикации я дополню слова Алексея и расскажу метод проще.
Для кого:
Статья направлена в помощь людям которые не работали с Git, GitHub, и хотят освоить в общих чертах как можно быстрее и без сложностей начать работу с ними.
О тексте:
Старался писать проще и с большим количеством скриншотов и пояснений. Ведь лучше, когда они есть чем, когда их нет и о чем-то приходится догадываться.
Итак, немного теории чтоб понять, что делать дальше:
- Visual Studio 2015 года или новее
- Подключение к интернету
- Несколько гигабайт памяти на жестком диске
Инструкция:
-
Переходим в меню Tools → Extensions and Updates → откроется вкладка Installed → если в расширениях отсутствует «GitHub Extension for Visual Studio» идем дальше, иначе перейдите к пункту следующему пункту инструкции → вкладка Online → ищем в поиске наше расширение → скачиваем и устанавливаем.
После, с GitHub копируем ссылку:
-
Может возникнуть вопрос – Что значат другие иконки?
Ответ:
Карандаш для того чтоб фиксировать изменения локально (commit). Используйте когда есть что сохранить, то есть код или файлы изменились.
Дополнительно:
Чтоб GitHub верно отображал русские комментарии (если есть) при просмотре кода через сайт нужно сделать следующее:
Cоветую всё-таки изучить Git Bash.
Я старался писать как можно понятнее, если что-то не так, то поправьте в комментариях!
На этом все. Спасибо за внимание!
Git и TFS: история дружбы
Git — распределенная система контроля версий, где каждый разработчик имеет копию всего репозитория, что означает отличную поддержку оффлайн-разработки. Еще у Git есть хорошая, понятная модель бранчинга, и разработчику не надо долго думать о том, как создавать локальные или приватные бранчи для удобства работы. В общем, с Git все хорошо, и на MSDN есть посвященный Git бранч.
Проект Git в Team Foundation Service
После регистрации в TFS на странице команд есть новая кнопка — New Team Project + Git. Пара кликов — и проект Git готов.
Собственно, на этом все. :) Но это — верхушка айсберга, внутри интеграция гораздо сложнее. Дальше — про то, как из Visual Studio подключиться и поманипулировать нашим Git-проектом.
Visual Studio и Git
Делаю сразу оговорку — Visual Studio — не замена существующему UI Git. Visual Studio может быть заменой, но чаще используется в совокупности с другими средствами. Если Git был создан внутри TFS, то у разработчика появляются некоторые фичи, пришедшие из TFS, например, Work Items, но VS спокойно работает с любыми локальными репозиториями и заслуженными Git-деятелями в лице GitHub и BitBucket.
Для подключения к Git-репозиторию достаточно нажать TEAM | Connect to Team Foundation Server.
Откроется Team Explorer. Как видите, у меня уже есть склонированный (с GitHub) репозиторий, и тут же — репозиторий TFS. Для клонирования нового репозитория Git можно нажать Clone и ввести данные подключения.
Для подключения аккаунта Visual Studio Online нажмем Select Team Projects, выберем аккаунт и установим, какой репозиторий надо подтянуть к нам в VS.
После подключения проектов выберем нужный и нажмем в контекстном меню кнопку Clone.
На этом процесс клонирования закончен — в бранче Local Git Repositories в Team Explorer появится склонированный репозиторий. Повторюсь — с помощью Clone можно клонировать любой Git-репозиторий.
Еще одна интересная фича интеграции Visual Studio и Git — это возможность создать новый проект и сразу добавить его в локальную систему контроля версий. Для этого при создании нового проекта в VS достаточно отметить Add to source control.
Перед тем, когда вы будете коммитить что-то в репозиторий, нужно установить данные для коммитов — нажать на Changes и предупреждение о том, что нужно ввести данные.
Полезные функции на этой странице есть еще внутри Repository Settings — можно настроить .gitIgnore и .gitattributes.
Дальше можно коммитить.
Чтобы сделать Pull и получить последние апдейты от команды, нужно перейти на Commits и нажать Fetch для того, чтобы сначала посмотреть, что там вообще придет (и есть ли чему придти).
Все хорошо — нажмем Pull и получим последний апдейт. Дополнительные сведения можно найти тут — Pull changes from the team.
Использование бранчей
Для использования бранчей в Team Explorer выделена специальная секци Branches.
После подключения к репозиторию доступна только master.
Создадим новый бранч, нажав New Branch.
Поскольку бранчи Git локальны до момента Push, новый бранч будет размещен в Unpublished Branches. Поменять бранч для коммитов можно на уже упоминавшейся выше странице Commits.
Замерджить контент можно, нажав Merge и выбрав бранчи. Подробнее про бранчи и мерджи — Git Branching.
Если в процессе мерджа или пулла возникнут конфликты, они тут же могут быть разрезолвены (самые простые, конечно).
Для просмотра истории достаточно нажать View History в контекстном меню бранча.
По нажатию на коммит получим подробные сведения о том, что произошло.
Многое из этого также доступно на портале TFS. Для того, чтобы перейти туда из VS, нужно на странице проекта в Team Explorer нажать Web Portal.
Уже на портале можно изучить общее состояние репозитория…
… и подробную информацию об этих коммитах.
Резюме
Мы кратко посмотрели на то, как выглядит очень простой процесс взаимодействия Visual Studio и Git. Как говорилось в самом начале, плод интеграции Git в Visual Studio — это не намек на то, что Visual Studio полностью заменит рабочий процесс. Но то, что одна из самых популярных IDE стала отлично поддерживать одну из самых популярных систем контроля версий — это, на мой взгляд, замечательный факт, и обязательно понравится тем, кто использует и то и другое.
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:
-
- 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. - The settings in this section configure Git-related settings and preferences that are managed by Visual Studio.
How to configure settings
To configure Git settings in Visual Studio, choose Settings from the top-level Git menu.
Choose Git Global Settings or Git Repository Settings to view and configure global-level or repository-level settings.
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.
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.
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.
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.
Provide your user name and email, then choose OK to save.
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)
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.
Set Prune remote branches during fetch to True (recommended). Select Ok to save.
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.
- Preserve: Rebase without flattening locally created merge commits.
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.
Set Rebase local branch when pulling to the desired setting, and select OK to save.
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
- 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.
From the Git menu, go to Settings. Go to Git Global Settings to configure this setting.
Set Cryptographic network provider to the desired value, and select OK to save.
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:
From the Git menu, go to Settings. Go to Git Global Settings to configure this setting.
Set Credential helper to the desired value, and select OK to save.
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.
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.
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.
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.
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.
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.
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.
- 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.
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.
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.
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.
See also
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.
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:
-
- 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. - The settings in this section configure Git-related settings and preferences that are managed by Visual Studio.
How to configure settings
To configure Git settings in Visual Studio, choose Settings from the top-level Git menu.
Choose Git Global Settings or Git Repository Settings to view and configure global-level or repository-level settings.
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.
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.
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.
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.
Provide your user name and email, then choose OK to save.
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)
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.
Set Prune remote branches during fetch to True (recommended). Select Ok to save.
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.
- Preserve: Rebase without flattening locally created merge commits.
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.
Set Rebase local branch when pulling to the desired setting, and select OK to save.
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
- 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.
From the Git menu, go to Settings. Go to Git Global Settings to configure this setting.
Set Cryptographic network provider to the desired value, and select OK to save.
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:
From the Git menu, go to Settings. Go to Git Global Settings to configure this setting.
Set Credential helper to the desired value, and select OK to save.
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.
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.
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.
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.
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.
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.
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.
- 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.
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.
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.
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.
See also
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.
Читайте также: