-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Release sdk status #22260
Release sdk status #22260
Conversation
…into release-sdk-status
…dk-for-python into release-sdk-status
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: |
/check-enforcer override |
1 similar comment
/check-enforcer override |
* initial * fix * fix * print fix * debug * debug * debug * debug * fix html link * print format * Add some comments * swagger default branch changes to main * Update main.py * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * Update release_sdk_status.yml for Azure Pipelines * Update release_sdk_status.yml for Azure Pipelines * test * test * fix * fix * fix * fix path * fix path * fix title * fix failed * fix failed * fix * fix multi api describe * test * test * fix fake * test * test * test * test * test Co-authored-by: msyyc <70930885+msyyc@users.noreply.github.com> Co-authored-by: Zed <601306339@qq.com>
* initial * fix * fix * print fix * debug * debug * debug * debug * fix html link * print format * Add some comments * swagger default branch changes to main * Update main.py * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * test * Update release_sdk_status.yml for Azure Pipelines * Update release_sdk_status.yml for Azure Pipelines * test * test * fix * fix * fix * fix path * fix path * fix title * fix failed * fix failed * fix * fix multi api describe * test * test * fix fake * test * test * test * test * test Co-authored-by: msyyc <70930885+msyyc@users.noreply.github.com> Co-authored-by: Zed <601306339@qq.com>
Rp soft delete (Azure#22260) * Adds base for updating Microsoft.RecoveryServices from version stable/2023-01-01 to version 2023-02-01 * Updates readme * Updates API version in new specs and examples * Adds RP Soft delete related API changes * added ExtendedLocation to IaasVMRestoreRequest (Azure#22468) * fixed lint error (Azure#22483) * - adding changes for private endpoint support in get, list Rp and trigger restore. * -fixing data type * fixing validation errors * Added changed for Secured VM details and Security Type (Azure#22848) --------- Co-authored-by: shesamian <107954668+shesamian@users.noreply.github.com> Co-authored-by: Arpit Jain <46751982+arpja@users.noreply.github.com> Co-authored-by: Saksham Arora <125243942+sakshamarora9575@users.noreply.github.com>
count test coverage and multiapi/singleapi