Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes ISSUE #9607 but for Azure DevOps
Issue was created for BitBucket but in the comments discussions were made to create the same for other providers. Azure DevOps also has a less popular version of Azure DevOps Server that can be installed on-premise with self-signed certificates.
Was based on a previously merged PR #19002 that did the same for BitBucketServer & GitLab.
Checklist:
[ x ] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
[ x ] The title of the PR states what changed and the related issues number (used for the release note).
[ x ] The title of the PR conforms to the Toolchain Guide
[ x ] I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
[ x ] Does this PR require documentation updates?
[ x ] I've updated documentation as required by this PR.
[ x ] I have signed off all my commits as required by DCO
I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
My build is green (troubleshooting builds).
My new feature complies with the feature status guidelines.
I have added a brief description of why this PR is necessary and/or what this PR solves.
Optional. My organization is added to USERS.md.
Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).