{CI} Use target_commitish branch in release to trigger Reference Docs CI#31011
Merged
wangzelin007 merged 4 commits intoAzure:devfrom Mar 18, 2025
xmdanni:tag-trigger
Merged
{CI} Use target_commitish branch in release to trigger Reference Docs CI#31011wangzelin007 merged 4 commits intoAzure:devfrom xmdanni:tag-trigger
wangzelin007 merged 4 commits intoAzure:devfrom
xmdanni:tag-trigger
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
Collaborator
|
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
requested review from
Pan-Qi,
bebound,
jiasli,
jsntcy,
kairu-ms,
wangzelin007 and
yonzhan
wangzelin007
approved these changes
Mar 13, 2025
| AdoProject: ${{secrets.ADO_DocsReference_Project}} | ||
| AdoPipelineId: ${{secrets.ADO_DocsReference_JumpPipeline_ID}} | ||
| CheckInterval: 60 | ||
| AdoLatestPipelineId: ${{secrets.ADO_DocsReference_Latest_Pipeline_ID}} |
Member
There was a problem hiding this comment.
LGTM.
We need a quick call or meeting to setup the new github action secrets.
AllyW
reviewed
Mar 17, 2025
AllyW
approved these changes
Mar 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related command
Description
To support LTS package docs auto generation from package release, and make LTS and latest co-exist on Learn site docs reference.
To-do by azure-cli dev: delete secrets.ADO_DocsReference_JumpPipeline_ID, add secrets.ADO_DocsReference_LTS_Pipeline_ID & secrets.ADO_DocsReference_Latest_Pipeline_ID.
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.