-
Notifications
You must be signed in to change notification settings - Fork 524
[ReleasePR attestation] change the value of license header for go SDK #1323
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
1f7e6b7 to
ad09e12
Compare
ad09e12 to
5874476
Compare
5874476 to
ad60136
Compare
ghost
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.
This PR has been auto-approved by the @msftbot for the azure-resource-manager-schemas repo.
One final private link connection fix, hopefully the last (#12307) * One final private link connection fix, hopefully the last * Undid some incorrect changes that snuck in * Fixed two data plane python typos * FInal python changes, hopefully * Put back unreferenced types to make breaking change vaidator happy * Next attempt at changes - added back the privateEndpointConnections API which should generate the correct aliases * Pull request CI fixes * Pull request CI fixes
ad60136 to
8de342a
Compare
ghost
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.
This PR has been auto-approved by the @msftbot for the azure-resource-manager-schemas repo.
|
Hello @msftbot[bot]! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
|
Apologies, while this PR appears ready to be merged, I've been configured to only merge when all checks have explicitly passed. The following integrations have not reported any progress on their checks and are blocking auto-merge:
These integrations are possibly never going to report a check, and unblocking auto-merge likely requires a human being to update my configuration to exempt these integrations from requiring a passing check. Give feedback on thisFrom the bot dev teamWe've tried to tune the bot such that it posts a comment like this only when auto-merge is blocked for exceptional, non-intuitive reasons. When the bot's auto-merge capability is properly configured, auto-merge should operate as you would intuitively expect and you should not see any spurious comments. Please reach out to us at [email protected] to provide feedback if you believe you're seeing this comment appear spuriously. Please note that we usually are unable to update your bot configuration on your team's behalf, but we're happy to help you identify your bot admin. |
Create to sync Azure/azure-rest-api-specs#13886
ReCreate this PR