woodpecker/pipeline/frontend/yaml/constraint
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
..
constraint.go Rework status constraint logic for successes (#1515) 2023-01-02 06:36:57 +01:00
constraint_test.go Rework status constraint logic for successes (#1515) 2023-01-02 06:36:57 +01:00