Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @yanzhudd, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
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>
|
|
There was a problem hiding this comment.
Pull request overview
Updates repository ownership mappings to reflect a change in responsible maintainers for several areas, ensuring PR review requests are routed to the correct people via GitHub CODEOWNERS.
Changes:
- Replaced
@zhoxing-mswith@yanzhuddfor/src/index.jsonand several extension directory paths in CODEOWNERS. - Updated ownership for
/src/interactive/and multiple other extension folders to align with the new owner assignment.
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
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.