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
Verify formatting in pipelines #10684
Conversation
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.
cACK, code LGTM
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.
cACK
I can add this, but GitHub action is easier and also the future. Can you try to do the same with GitHub Actions? |
Sure, I just thought that you use Azure for a very strong reason. |
There was but it seems like not a problem anymore since we already added actions and nobody complained. |
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.
David is right. We're moving to GitHub actions for a while now. This'd be a step in the wrong direction.
c11e71b
to
edfd09d
Compare
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.
@molnard, well, isn't this PR intending to improve code quality? So, in addition to the pipeline I fixed all formatting issues we had (mostly spaces and usings) and a few CA2000 warnings. If I did all of these changes and checked them using |
Can you tell me why the formatting pipeline fails here? |
That pull requests adds formatting check to Azure pipelines, so reviewers won't spend their time on that task. Perhaps, it will require formatting the existing code, but maybe not.
Rules can be configured though
.editoconfig
.