Closed edwardsp closed 2 weeks ago
Thank you for your contribution! We will review the pull request and get back to you soon.
Hi @edwardsp, Please write the description of changes which can be perceived by customers into HISTORY.rst. If you want to release a new extension version, please update the version in setup.py as well.
For more info about extension versioning, please refer to Extension version schema
Thank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey
[Release] Update index.json for extension [ bastion ] : https://dev.azure.com/azclitools/release/_build/results?buildId=166024&view=results
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
The current behaviour is to block once there is a connection and this doesn't work if you are forwarding a web server as the browser will start multiple connections.
There has been an issue open for some time on the main azure-cli repository for this issue: https://github.com/Azure/azure-cli/issues/24600
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
.