File tree Expand file tree Collapse file tree 1 file changed +56
-0
lines changed Expand file tree Collapse file tree 1 file changed +56
-0
lines changed Original file line number Diff line number Diff line change 5353 check : cancelled
5454 comment : false
5555
56+ - pipeline :
57+ name : check-review
58+ description : |
59+ Newly uploaded patchsets enter this pipeline after getting an
60+ initial review to allow for secrets usage.
61+ manager : independent
62+ post-review : true
63+ trigger :
64+ github :
65+ # Run this pipeline on new/changed pull requests
66+ - event : pull_request
67+ action :
68+ - opened
69+ - changed
70+ - reopened
71+ # Run in response to a pull request comment "recheck"
72+ - event : pull_request
73+ action : comment
74+ comment : (?i)^\s*recheck\s*$
75+ # When using the checks API to report results, failed runs
76+ # will have a "re-run" button which emits this event.
77+ - event : check_run
78+ action : rerequested
79+ check : .*/check:.*
80+ start :
81+ github :
82+ check : ' in_progress'
83+ comment : false
84+ # It is recommended to use the checks API for consistency with
85+ # other common CI tools that integrate with Github. Results
86+ # will appear on the "checks" tab of PR and changes. There is
87+ # generally no need to have Zuul leave comments when using the
88+ # checks API.
89+ #
90+ # The older status API appears inline with the PR and can be
91+ # enabled by uncommenting the "status:" in the various
92+ # sections below. You should choose one or the other
93+ # depending on project preferences.
94+ #
95+ # status: 'pending'
96+ # comment: false
97+ success :
98+ github :
99+ check : ' success'
100+ comment : false
101+ # status: 'success'
102+ failure :
103+ github :
104+ check : ' failure'
105+ comment : false
106+ # status: 'failure'
107+ dequeue :
108+ github :
109+ check : cancelled
110+ comment : false
111+
56112- pipeline :
57113 name : gate
58114 description : |
You can’t perform that action at this time.
0 commit comments