Update Validate-Formatting to use black output vs git diff - #19625
Conversation
…in a git diff can be ignored.
|
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
|
/azp run python - template |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/check-enforcer override |
Here is a failing build. the reason this is happening is because the script currently will break on anything being different at all. Unfortunately the
templatepipeline actually modifies theversionand thechangelog, so this means that thevalidate formattingfinds a git diff and explodes.Do you have any issues with this Sean Kane (@seankane-msft) ?