woodpecker/pipeline/frontend/yaml/compiler
Stephen Muth bc87208a33
Rework status constraint logic for successes (#1515)
Since "success" and "failure" are the only two possible values, and
"success" is considered to be included by default, the existing code can
also be simplified a little.

This has the side effect of ignoring the "exclude" part of the
constraint completely. I put it in the tests just to make sure the
workaround in
https://github.com/woodpecker-ci/woodpecker/issues/1181#issuecomment-1347253585
continues to work as expected, but couldn't think of any legitimate use
cases for it.

Fixes #1181
2023-01-02 06:36:57 +01:00
..
settings Add support sub-settings and secrets in sub-settings (#1221) 2022-10-03 19:25:43 +02:00
cacher.go Move plugin config to root.pipeline.[step].settings (#464) 2021-12-04 16:44:18 +01:00
compiler.go Support plugin-only secrets (#1344) 2022-10-27 04:21:07 +02:00
compiler_test.go Support plugin-only secrets (#1344) 2022-10-27 04:21:07 +02:00
convert.go Rework status constraint logic for successes (#1515) 2023-01-02 06:36:57 +01:00
image.go Move cncd/pipeline/pipeline/ to pipeline/ (#347) 2021-09-24 13:18:34 +02:00
image_test.go Move cncd/pipeline/pipeline/ to pipeline/ (#347) 2021-09-24 13:18:34 +02:00
option.go Rename build to pipeline in code (#1224) 2022-10-18 03:24:12 +02:00
option_test.go Rename remote to forge (#1357) 2022-11-05 00:35:06 +01:00