1format: v0.1-alpha
2minimumCheckRuns: 1
3timeout: 10
4message: >
5 This pull request is protected by [Check Enforcer](https://aka.ms/azsdk/check-enforcer).
6
7 # What is Check Enforcer?
8
9 Check Enforcer helps ensure all pull requests are covered by at least one
10 check-run (typically an Azure Pipeline). When all check-runs associated
11 with this pull request pass then Check Enforcer itself will pass.
12
13 # Why am I getting this message?
14
15 You are getting this message because Check Enforcer did not detect any
16 check-runs being associated with this pull request within five minutes. This
17 may indicate that your pull request is not covered by any pipelines and so
18 Check Enforcer is correctly blocking the pull request being merged.
19
20 # What should I do now?
21
22 If the **check-enforcer** check-run is not passing and all other check-runs
23 associated with this PR are passing (excluding _license-cla_) then you could
24 try telling _Check Enforcer_ to evaluate your pull request again. You can
25 do this by adding a comment to this pull request as follows:
26
27 ```
28 /check-enforcer evaluate
29 ```
30
31 Typically evaulation only takes a few seconds. If you know that your pull
32 request is not covered by a pipeline and this is expected you can override
33 Check Enforcer using the following command:
34
35 ```
36 /check-enforcer override
37 ```
38
39 Note that using the override command triggers alerts so that follow-up
40 investigations can occur (PRs still need to be approved as normal).
41
42 # What if I am onboarding a new service?
43
44 Often, new services do not have validation pipelines associated with them.
45 In order to bootstrap pipelines for a new service, please perform following steps:
46
47 ## For track 2 SDKs
48 Issue the following command as a pull request comment:
49
50 ```
51 /azp run prepare-pipelines
52 ```
53
54 This will run a pipeline that analyzes the source tree and creates the
55 pipelines necessary to build and validate your pull request. Once the pipeline
56 has been created you can trigger the pipeline using the following comment:
57
58 ```
59 /azp run go - [service] - ci
60 ```
View as plain text