-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Changes required for testing upgrades to cspell #53947
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
Conversation
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 introduces changes to support testing upgrades to cspell (the spell checking tool) across the Azure SDK repository. The changes include adding a new spell check script for public API surfaces, adding cspell configuration for the recoveryservices SDK, and enabling cspell upgrade verification in the CI pipeline.
Key Changes
- New PowerShell script (
spell-check-public-api.ps1) to spell check all public API surface files - Added cspell configuration for the recoveryservices SDK to whitelist the "bcdr" term
- Enabled
EnableCspellUpgradeVerificationparameter in the CI pipeline's spell check step
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| eng/scripts/spell-check-public-api.ps1 | New script to perform spell checking on all public API surface files (*.cs files in api/ directories) |
| sdk/recoveryservices/cspell.yaml | New cspell configuration file that whitelists "bcdr" term for the recoveryservices SDK |
| eng/pipelines/templates/jobs/ci.yml | Adds EnableCspellUpgradeVerification parameter to the spell checking step for testing cspell upgrades |
2fcdf3c to
a45d38f
Compare
Depends on Azure/azure-sdk-tools#12910