-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Prepare for new azdev #6505
Prepare for new azdev #6505
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
Hi @bebound, |
Thank you for your contribution! We will review the pull request and get back to you soon. |
# line break after binary operator effect on readability is subjective | ||
W504 | ||
# line break occurred before a binary operator | ||
W503 |
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.
No idea why lots of W503 errors are raised in Static Analysis
test.
/mnt/vss/_work/1/s/src/ssh/azext_ssh/ssh_info.py:144:26: W503 line break before binary operator
/mnt/vss/_work/1/s/src/datafactory/azext_datafactory/manual/custom.py:130:13: W503 line break before binary operator
In this PR, we found that the extension style check is not working for a long time.
, which raises
This is fixed in #6509 |
Check if CI works in new azdev Azure/azure-cli-dev-tools#359
As pylint version bumps to 2.17, many new rules are added. I guess the service team may need to fix their code style when PR is submitted.