Conversation
️✔️AzureCLI-FullTest
|
|
Hi @AllyW, |
️✔️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>
|
| merge_base=$(git merge-base HEAD "$base_branch_pre"/"$base_branch") | ||
| echo merge_base: "$merge_base" | ||
| # check azdev style on diff mod | ||
| azdev style |
There was a problem hiding this comment.
How is azdev style on diff mode without specifying these arguments?
Git Arguments
--repo : Path to the Git repo to check.
--src : Name of the Git source branch to check (i.e. master or upstream/master).
--tgt : Name of the Git target branch to check (i.e. dev or upstream/dev).
There was a problem hiding this comment.
For now azdev style runs in full mode, to be consistent with ado pipeline: https://github.com/Azure/azure-cli/blob/dev/azure-pipelines.yml#L1055


Related command
Description
Add
azdev style & lintertask into github workflow, with no dependency on token or pr write permission.Test pr: AllyW#2
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.