Conversation
|
Validation for Breaking Change Starting...
Thanks for your contribution! |
|
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>
|
microsoft-github-policy-service
bot
added
the
customer-reported
|
Thank you for your contribution @Bodlux! We will review the pull request and get back to you soon. |
Responsible Disclosure NoticeThis automated comment was generated as part of an authorized security research engagement. It demonstrates that the Finding: An external contributor can control the content of this automated comment and manipulate PR labels by modifying artifact files during the version-cal job, which checks out and executes code from the pull request head branch. This issue has been reported to the Microsoft Security Response Center (MSRC) as part of responsible disclosure. No secrets were accessed and no unauthorized modifications were made. Researcher: Bodlux | Run ID: 24317128999 | Timestamp: 2026-04-12T21:48:06.541622 |
2 participants
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.