-
Notifications
You must be signed in to change notification settings - Fork 221
Allow save-package-properties to exit 0 #8879
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
Conversation
scbedd
left a comment
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.
I especially like the fact that the old style "service directory oriented" will still fail if detects no package. Which IS reasonable. This seems g2g to me.
|
The following pipelines have been queued for testing: |
Sync eng/common directory with azure-sdk-tools for PR Azure/azure-sdk-tools#8879 See [eng/common workflow](https://github.com/Azure/azure-sdk-tools/blob/main/eng/common/README.md#workflow) Co-authored-by: Patrick Hallisey <[email protected]>
|
/check-enforcer override ADO check suite not updating. Completed successfully |
| $outputPath = Join-Path -Path $outDirectory "$configFilePrefix.json" | ||
| Write-Host "Output path of json file: $outputPath" | ||
| $outDir = Split-Path $outputPath -parent | ||
| if (-not (Test-Path -path $outDir)) |
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.
Is there any case where this directory doesn't already exist?
Allow save-package-properties to exit 0 when PRs produce no package changes