summaryrefslogtreecommitdiff
path: root/releasenotes/notes/fix-exclude-include-priority-ea4a21ab1e53cb4a.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'releasenotes/notes/fix-exclude-include-priority-ea4a21ab1e53cb4a.yaml')
-rw-r--r--releasenotes/notes/fix-exclude-include-priority-ea4a21ab1e53cb4a.yaml12
1 files changed, 12 insertions, 0 deletions
diff --git a/releasenotes/notes/fix-exclude-include-priority-ea4a21ab1e53cb4a.yaml b/releasenotes/notes/fix-exclude-include-priority-ea4a21ab1e53cb4a.yaml
new file mode 100644
index 000000000..9dd238faf
--- /dev/null
+++ b/releasenotes/notes/fix-exclude-include-priority-ea4a21ab1e53cb4a.yaml
@@ -0,0 +1,12 @@
+---
+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.