Commit b33586f
committed
/deploy: use separate check runs for each architecture
For MSys packages we start two build workflows, that can succeed or fail
independently from one another. Representing their combined outcome in one
check run, whose result only depends on the first workflow to finish is not
great. Using one check run for each workflow makes it easier to see which
workflow failed when one of them fails and allows us to see at a glance if
one of the workflows is still running after the other one completed.
Signed-off-by: Matthias Aßhauer <mha1993@live.de>1 parent 01a9475 commit b33586f
1 file changed
Lines changed: 34 additions & 12 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
134 | 134 | | |
135 | 135 | | |
136 | 136 | | |
137 | | - | |
138 | | - | |
139 | | - | |
140 | | - | |
141 | | - | |
142 | | - | |
143 | | - | |
144 | | - | |
145 | | - | |
146 | | - | |
147 | | - | |
148 | 137 | | |
149 | 138 | | |
150 | 139 | | |
| |||
173 | 162 | | |
174 | 163 | | |
175 | 164 | | |
| 165 | + | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
| 170 | + | |
| 171 | + | |
| 172 | + | |
| 173 | + | |
| 174 | + | |
| 175 | + | |
176 | 176 | | |
177 | 177 | | |
178 | 178 | | |
179 | 179 | | |
| 180 | + | |
| 181 | + | |
| 182 | + | |
| 183 | + | |
| 184 | + | |
| 185 | + | |
| 186 | + | |
| 187 | + | |
| 188 | + | |
| 189 | + | |
| 190 | + | |
| 191 | + | |
| 192 | + | |
| 193 | + | |
| 194 | + | |
| 195 | + | |
| 196 | + | |
| 197 | + | |
| 198 | + | |
| 199 | + | |
| 200 | + | |
| 201 | + | |
180 | 202 | | |
181 | 203 | | |
182 | 204 | | |
| |||
262 | 284 | | |
263 | 285 | | |
264 | 286 | | |
265 | | - | |
| 287 | + | |
0 commit comments