-
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
Migrating to AAZ Dev Tools for communication control plane operations #6432
Conversation
Hi @jorge-beauregard, |
Thank you for your contribution! We will review the pull request and get back to you soon. |
5ff20a0
to
5bc4409
Compare
src/communication/azext_communication/aaz/latest/communication/_create.py
Show resolved
Hide resolved
a71bfd7
to
7c5b674
Compare
src/communication/azext_communication/aaz/latest/communication/_create.py
Show resolved
Hide resolved
54aef98
to
f79db98
Compare
f79db98
to
1bb36b1
Compare
1bb36b1
to
2fc8faa
Compare
src/communication/azext_communication/aaz/latest/communication/_create.py
Outdated
Show resolved
Hide resolved
[Release] Update index.json for extension [ communication ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=70617&view=results |
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?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
.