-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
{vm-repair} Add code documentation and fix Unbound exceptions #8124
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
Hi @Sandido, |
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
@yanzhudd , please re-review and merge if possible. |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
[Release] Update index.json for extension [ vm-repair ] : https://dev.azure.com/msazure/One/_build/results?buildId=109101394&view=results |
This PR is an example of using AI to add documentation to code and Github Copilot to find bugs to fix.
This PR adds code documentation to the big custom.py file.
This also fixes an Unbound exception bug in the existing_rg and copy_disk_id variables.
Fixed a duplicate test name error.
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 azdev
required)python scripts/ci/test_index.py -q
locally? (pip install wheel==0.30.0
required)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.json
automatically.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
.