Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @msarfraz, |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
There was a problem hiding this comment.
Pull request overview
Updates the shared Azure Pipelines variables template to move the repository’s Windows jobs from the 2019 agent pool to the 2022 agent pool, impacting all pipelines that reference variables.windows_pool.
Changes:
- Changed
windows_poolfrompool-windows-2019topool-windows-2022in the shared variables template.
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
windows pool upgraded to 2022 in pipeline
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.jsonautomatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json.