{CI} Use GitHub Actions to trigger the ADO OneBranch Extension Release Pipeline

[wangzelin007]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

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.

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @wangzelin007,
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.

[azure-client-tools-bot-prd]

Hi @wangzelin007,
Since the current milestone time is less than 7 days, this pr will be reviewed in the next milestone.

[yonzhan]

CI

[bebound]

Although this is the only solution to trigger ADO pipeline.
However, it seems that it lacks batch CI support, posing a risk of earlier commits task overwriting index.json from later ones.

---

Can we use concurrency to eliminate the overwrite probability? For example, only one job can run, and after trigger ADO, it waits for several minutes?

[wangzelin007]

Although this is the only solution to trigger ADO pipeline. However, it seems that it lacks batch CI support, posing a risk of earlier commits task overwriting index.json from later ones.

Can we use concurrency to eliminate the overwrite probability? For example, only one job can run, and after trigger ADO, it wait for several minutes?

Thank you!
This is exactly what I'm looking for~

[wangzelin007]