Bot intelligently sets excluded labels despite exclusion when keyword detection is enabled
Summary
In the "Intelligently Assign Labels" section we have added a lot of labels to exclude. One of them is the text "security" and was already there since a while.
However we noticed yesterday that the bot had just assigned said label to the issue https://github.com/owncloud/core/issues/30762.
Steps to reproduce
- Open repository config in Gitmate (cog icon)
- Scroll to ection "Intelligently Assign Labels"
- Set the following labels: "status/STALE, QA-ready, backport-request, security, ready, 1 - To Develop, 2 - Developing, 3 - To Review, 4 - To Release, bounty, backport-request, blue-ticket, Drone, enhancement-PM, green-ticket, in progress, jenkins, orga, p1 - urgent, p2 - high, p3 - medium, p4 - low, PM prio 1, PM prio 2, PM prio 3, purple-ticket, QA-blocker, QA-known, QA-ready, QA-testing, QA, ready, security, sev1-critical, sev2-high, sev3-medium, sev4-low, tested, Waiting Internal, Waiting, won't fix"
And just now I notice that the label appears twice. Shouldn't be a problem still.
What is the current bug behavior?
After a day or so Gitmate still sets the "security" label.
What is the expected correct behavior?
Security label should never be set automatically.
Relevant links and/or screenshots
See https://github.com/owncloud/core/issues/30762. Repo config (if you have access): https://gitmate.io/repo/13112
Output of checks
This bug happens on https://gitmate.io
Possible fixes
Maybe our exclusion line is too long. Or maybe the special characters (slashes) is messing with the config parser ? Or is it the fact that the "security" label appears twice in the list ?