Commit d33a0e9
committed
otp: add ruleset check in main.yaml
gh rulesets allow owners of the project to set which checks (jobs) must
have completed successfully before allowing merging of a pull request.
however, the current ruleset contains jobs that are optionally executed,
meaning that they depend on a `if:` condition.
Jobs in a ruleset are supposed to always be executed. This means that
there are (at times) pull requests where one needs to skip the ruleset
constraint because the job in the ruleset was simply skipped.
To overcome this limitation, we write in `main.yaml` a new job that
considers all jobs that should be checked for success, and consider
skipped jobs as successful as well. Failed or cancelled jobs will be
consider a failure.1 parent ade6efa commit d33a0e9
1 file changed
Lines changed: 47 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
321 | 321 | | |
322 | 322 | | |
323 | 323 | | |
| 324 | + | |
| 325 | + | |
| 326 | + | |
| 327 | + | |
| 328 | + | |
| 329 | + | |
| 330 | + | |
| 331 | + | |
| 332 | + | |
| 333 | + | |
| 334 | + | |
| 335 | + | |
| 336 | + | |
| 337 | + | |
| 338 | + | |
| 339 | + | |
| 340 | + | |
| 341 | + | |
| 342 | + | |
| 343 | + | |
| 344 | + | |
| 345 | + | |
| 346 | + | |
| 347 | + | |
| 348 | + | |
| 349 | + | |
| 350 | + | |
| 351 | + | |
| 352 | + | |
| 353 | + | |
| 354 | + | |
| 355 | + | |
| 356 | + | |
| 357 | + | |
| 358 | + | |
| 359 | + | |
| 360 | + | |
| 361 | + | |
| 362 | + | |
| 363 | + | |
| 364 | + | |
| 365 | + | |
| 366 | + | |
| 367 | + | |
| 368 | + | |
| 369 | + | |
| 370 | + | |
0 commit comments