a557e140b1
Per the documentation, include-branches should be able to override exclude-branches, but this was not the case in the way the code was written. Rework the code to correct this, and also add a test to ensure it works as documented Change-Id: I2e23b1533c67ccf84b4d6a36f5a003adc7b3e45a
13 lines
549 B
YAML
13 lines
549 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
Fixes `tenant.untrusted-projects.<project>.include-branches` being lower
|
|
priority than `tenant.untrusted-projects.<project>.exclude-branches` to
|
|
match the documentation and expected user behavior.
|
|
|
|
This only affects projects that are using both `include-branches` and
|
|
`exclude-branches` at the same time. Now, `include-branches` has priority
|
|
over `exclude-branches` for any branches that match both. Practically
|
|
speaking, this means that `exclude-branches` is ignored if
|
|
`include-branches` is set.
|