Make Azure Pipelines use document scope #548
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@vtbassmatt Thanks for the contribution! This will make it into the GitLens 9 release coming very soon. |
ahmadalli
added a commit
to ahmadalli/vscode-gitlens
that referenced
this pull request
Aug 6, 2019
it's the same as gitkraken#548 for ansible language
8 tasks
eamodio
pushed a commit
that referenced
this pull request
Aug 12, 2019
it's the same as #548 for ansible language
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi. I'm a PM on Azure Pipelines. One of the features we've just shipped is an extension for VS Code to make it easier to author in our YAML-based format. For some reason, the same document parsed as YAML shows the right amount of GitLens entries, but when I switch over to treat it as Azure Pipelines, way too many entries get injected.
If there's a different way to solve this, I'm all for it! But this seemed to fix it properly in my local workspace settings, and I think it should be the default for GitLens users.
Thanks!