-
Notifications
You must be signed in to change notification settings - Fork 4k
Spelling Fixes #27954
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
Spelling Fixes #27954
Conversation
adding additional findings Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR addresses various spelling mistakes in pipeline configuration and scripts without any functional changes.
- Corrected typos in comments and logging messages.
- Standardized spelling of terms like “agents”, “commitId”, “Preparing”, and “folder”.
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
File | Description |
---|---|
.azure-pipelines/batch-generation.yml | Fixed typo “agnets” → “agents” in TODO comment. |
.azure-pipelines/azure-powershell-ci.yml | Corrected “commidId” → “commitId” in commented block. |
.azure-pipelines/PipelineSteps/BatchGeneration/prepare.ps1 | Updated “Prepareing” → “Preparing” in Write-Host message. |
.azure-pipelines/PipelineSteps/BatchGeneration/filter.ps1 | Fixed typo “filder” → “folder” in comment. |
Thank you for your contribution @ArieHein! We will review the pull request and get back to you soon. |
/azp list |
CI/CD Pipelines for this repository: |
/azp run azure-powershell - security-tools |
Azure Pipelines successfully started running 1 pipeline(s). |
Description
Additional spelling fixes. No Functional changes !
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.