build: fix spelling mistakes in pipeline scripts#299755
Open
thandorsa wants to merge 4 commits intomicrosoft:mainfrom
Open
build: fix spelling mistakes in pipeline scripts#299755thandorsa wants to merge 4 commits intomicrosoft:mainfrom
thandorsa wants to merge 4 commits intomicrosoft:mainfrom
Conversation
Contributor
📬 CODENOTIFYThe following users are being notified based on files changed in this PR: @lszomoruMatched files:
|
Author
|
@microsoft-github-policy-service agree |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This pull request fixes several spelling mistakes found in build and pipeline scripts:
accidential→accidental(build/lib/mangle/index.ts)occcured→occurred(build/azure-pipelines/win32/exec.ps1)Valiate→Validate(build/azure-pipelines/product-npm-package-validate.yml)These changes are minor and only affect comments and pipeline configuration, with no impact on VS Code functionality.
Testing Instructions: