-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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} Use target_commitish branch in release to trigger Reference Docs CI #31011
base: dev
Are you sure you want to change the base?
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
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>
|
@@ -25,56 +25,24 @@ jobs: | |||
env: | |||
AdoOrg: ${{secrets.ADO_DocsReference_Organization}} | |||
AdoProject: ${{secrets.ADO_DocsReference_Project}} | |||
AdoPipelineId: ${{secrets.ADO_DocsReference_JumpPipeline_ID}} | |||
CheckInterval: 60 | |||
AdoLatestPipelineId: ${{secrets.ADO_DocsReference_Latest_Pipeline_ID}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
We need a quick call or meeting to setup the new github action secrets.
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.