Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to override branch names #24

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Manuel-S
Copy link

Implemented #13. As there is no
Settings UI yet, it can only be changed at
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio{Visual Studio
Version}\AutoMerge. The setting is saved under the key
"branch_overrides" and takes JSON as described in the issue.

This changeset removes the FileSettingProvider and uses the Visual
Studio User Setting store instead, as this is the recommended way of
storing extension settings. The Settings-Object is now managed by MEF as
Singleton.
Implemented CDuke#13. As there is no
Settings UI yet, it can only be changed at
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\{Visual Studio
Version}\AutoMerge. The setting is saved under the key
"branch_overrides" and takes JSON as described in the issue.
@@ -16,6 +17,7 @@
using Microsoft.TeamFoundation.VersionControl.Client;
using Microsoft.TeamFoundation.VersionControl.Common;
using Microsoft.TeamFoundation.WorkItemTracking.Client;
using Microsoft.VisualStudio.ComponentModelHost;
using Microsoft.VisualStudio.Shell.Interop;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

error upon loading system.

@SergeLalonde
Copy link

Hi @Manuel-S
Did your change ever make it into a release? I'm using 0.2.6.10 with VS2019 (16.11.26).
I added a HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\16.11\AutoMerge key.
Under that, I added a REG_MULTI_SZ value called "branch_overrides".
The value is set to
[
{ "match": "Work/Sprints/(.)/(.)", "alias" : "Sprint-$1-$2" },
{ "match": "Releases/(.)/(.)", "alias" : "Release-$1-$2" },
]
It doesn't seem to have any effect in the display of the branches for either the list of changesets or the Target branches.
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants