Skip to content
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

[Fabric Bot] Service Contacts for Digital Twins #21128

Merged
merged 1 commit into from
Mar 31, 2022
Merged

Conversation

jsquire
Copy link
Member

@jsquire jsquire commented Mar 31, 2022

Summary

The focus of these changes is to update the service contacts for Digital Twins, incorporating the changes made in #2111.

The focus of these changes is to update the service contacts for Digital Twins, incorporating the changes made in [#2111](#2111).
@jsquire jsquire added EngSys This issue is impacting the engineering system. Client This issue points to a problem in the data-plane of the library. labels Mar 31, 2022
@jsquire jsquire added this to the [2022] April milestone Mar 31, 2022
@jsquire jsquire requested a review from christothes March 31, 2022 13:28
@jsquire jsquire requested a review from AlexGhiondea as a code owner March 31, 2022 13:28
@jsquire jsquire self-assigned this Mar 31, 2022
@jsquire
Copy link
Member Author

jsquire commented Mar 31, 2022

/check-enforcer override

@check-enforcer
Copy link

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:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

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 prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run js - [service] - ci

@jsquire jsquire merged commit ada5a56 into main Mar 31, 2022
@jsquire jsquire deleted the jsquire-patch-1 branch March 31, 2022 17:49
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-js that referenced this pull request Nov 3, 2022
Added Response Schema for Runbook Operation (Azure#21128)

* Added Response Schema for Runbook Operation

* Update resopnse of Runbook Operation

* Updated example to fix Avacado errors

* Update resopnse of Runbook Operation

* Updated example to fix Avacado errors

* Fix Lint diff errors

* Fix Avacado errors

* Fix Avacado errors

Co-authored-by: Sushil Upadhyay <supadhyay@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. EngSys This issue is impacting the engineering system.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants