Document possible Skip actions.
#23943
Conversation
|
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: |
Co-authored-by: Adam Ling (MSFT) <adam_ling@outlook.com>
|
There is no build associated with this changeset, going to override and merge. |
|
/check-enforcer override |
Release sql microsoft.sql 2022 11 01 preview (Azure#23802) * Adds base for updating Microsoft.Sql from version preview/2022-08-01-preview to version 2022-11-01-preview * Updates readme * Updates API version in new specs and examples * Add Swagger API changes required for progress-reporting related changes in DatabaseOperations (Azure#22669) * Update swagger (Azure#22715) * Follow-up Swagger API changes required for progress-reporting related changes in DatabaseOperations (Azure#22775) * Add Swagger API changes required for progress-reporting related changes in DatabaseOperations * Follow up changes required for progress-reporting related changes in DatabaseOperations * updated example file * Added Failed case in list-operations examples * Update Microsoft.Sql ManagedInstance 2022-11-01-preview Swagger Docs (Azure#22899) * Update Microsoft.sql ManagedInstance 2022-11-01-preview Swagger Docs * Address Swagger Validation Errors * Modify custom-words.txt * Manually updating arm-id format to match stable 2021-11-01 version * Adding provisioning state changes * fixing validation * adding missing space * Remove HTTP 200 from Start/Stop Actions as we only return HTTP 202 --------- Co-authored-by: Jovana Toroman <jtoroman@microsoft.com> * Update DateTime to ISO-8601 format in example file (Azure#22986) * Add Swagger API changes required for progress-reporting related changes in DatabaseOperations * Follow up changes required for progress-reporting related changes in DatabaseOperations * updated example file * Added Failed case in list-operations examples * Update DateTime to ISo-8601 format in example file * Enable TryPlannedBeforeForcedFailover for SQL DB Failover Group (Azure#22673) * Enable TryPlannedBeforeForcedFailover for SQL DB Failover Group * Modify example file * Add example * Fix ModelValidation issues * Fix ModelValidation issues * Add new controller * Modify example * Modify example * Update server name * Fix LintDiff * Fix model validation errors * Fix PostOperationAsyncResponseValidation, Unfix LroLocationHeader,ResourceNameRestriction * Fix PostOperationAsyncResponseValidation * Fix pending items * Update doc * Remove empty/unschematized object --------- Co-authored-by: subhrob <subhrob@microsoft.com> * [DO NOT MERGE] Add Archive option to LTR Policy for SQL DB (Azure#22697) * add archival changes to LTRPolicy * fix LongTermRetentionPolicies swagger file * fix check failures * redo swagger * Update swagger documentation for Managed Instance start-stop actions (Azure#22992) * Add NetworkSecurityPerimeterConfigurations Swagger (Azure#22960) * Add NetworkSecurityPerimeterConfigurations Swagger * Fixes round 1 * Fixes round 2 * Fixes Round 3 * Fixes Round 4 * Fix Round 5 * fixing enum (Azure#22995) Co-authored-by: Jovana Toroman <jtoroman@microsoft.com> * add changes (Azure#23120) * Carry all minor changes to dev sql microsoft.sql 2022 11 01 preview (Azure#23337) * Revert "add changes (Azure#23120)" This reverts commit 5c348d22f8fb6c29b7322e28ea78d665586f4135. Revert "[DO NOT MERGE] Add Archive option to LTR Policy for SQL DB (Azure#22697)" This reverts commit 559f7f474d944a92f6cb108eb433a05f3c53cd8e. * Carrying minor changes to release branch for Microsoft.Sql 2022-11-01-preview * Reverting DatabaseAdvisors * Further reverting problematic files * Reverting a few example files * Adding back arm-id to a few files * Reverting error message change in ManagedDatabaseRestoreDetails.json, Jobs.json,ServerDevOpsAudit.json, and TransparentDataEncryptions.json * Minor fixes for Turkey name change and missing x-ms-identifier (Azure#23637) * Fixing issues with a few breaking changes (Azure#23943) * Minor fixes for Turkey name change and missing x-ms-identifier * Adding back missing arm-id and other missing property issues causing breaking changes incorrectly. * Fixing prettier issue with ManagedDatabases.json * Fixing arm-id format in 4 examples * Adding missing location for 202 responses on sync examples --------- Co-authored-by: Ji Wang <wangjiprc@gmail.com> Co-authored-by: Mohit Agarwal <mohitagarwal@microsoft.com> Co-authored-by: GalGoldi72 <124780962+GalGoldi72@users.noreply.github.com> Co-authored-by: ilijadivljan-ms <122982104+ilijadivljan-ms@users.noreply.github.com> Co-authored-by: Jovana Toroman <jtoroman@microsoft.com> Co-authored-by: subhrob <subhro.bhattacharya@gmail.com> Co-authored-by: subhrob <subhrob@microsoft.com> Co-authored-by: CelinaJiangJXY <124339390+CelinaJiangJXY@users.noreply.github.com> Co-authored-by: beoberha <51964155+beoberha@users.noreply.github.com> Co-authored-by: toki95 <35834415+toki95@users.noreply.github.com>
@yunhaoling easing your confusion. Thanks for bringing this up.