-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
{CI} Fix verify ref docs #6507
{CI} Fix verify ref docs #6507
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
Hi @wangzelin007, |
CI |
I am not familiar with the logic of this CI task. Just out of curiosity, if the testing for |
The answer is yes, will remove extensions by the folllowing code:
|
This reverts commit f12d922.
* Revert "{CI} Update the --dependent-file parameter to be an optional argument to avoid introducing a breaking change. (#6521)" This reverts commit b442cf0. * Revert "{CI} Fix verify ref docs (#6507)" This reverts commit f12d922. * Revert "{CI} Fix command tree broken issue (#6573)" This reverts commit 3df4a81. * revert linter
This checklist is used to make sure that common guidelines for a pull request are followed.
Add a new parameter
dep_url (dependent url)
.If a extensionA is depend on another extensionB, will install extensionB first.
In this case, will install containerapp extension before verify ref docs for containerapp-preview extension.
Related command
General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally?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
.