-
-
Notifications
You must be signed in to change notification settings - Fork 85
Features/uuidv5 #73
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
Features/uuidv5 #73
Conversation
Doesn't work when extensionid and publisher are not specified
Guid inception required.
Enable in vsix publishing
This reverts commit d19a573.
|
Review status: all files reviewed at latest revision, all discussions resolved. Comments from Reviewable |
|
@willsmythe @wpschaub This is a special case, resurrected from an old branch. We have a couple of large clients who have a single VSTS account with links to a whole bunch of Azure resources. They are developing custom azure build and release tasks and want to publish experimental versions of an existing task to the same VSTS account. By default, this is prevented, as the taskIds aren't unique. This version will enable extension builders to generate a unique task ID using the PublisherID, ExtensionID and TaskName. I've tested these changes against my personal VSTS account already and it seems to work without issues. Feedback welcome. |
|
I would totally use this. We are also testing extensions in different versions in our account and have to take extra steps to make sure the task guids are unique acress extension versions. |
Auto-generates a UUID for build tasks to enable dev & prod in the same environment
This change is