broadcast_messages Target Path not filtered on command line
Summary
We experienced some strange behavior using Target Path
to assign specific broadcast message depending on a project path.
These do net get display in the UI but on the cli push even when not pushing to the selected repository.
Steps to reproduce
setup a broadcast_message with a Target Path push to another unrelated git repository results in the broadcast message to be displayed.
gitlab version is 12.9.3
Example Project
none
What is the current bug behavior?
the cli push to a repository not matching the defined Target Path
displays the broadcast_message.
What is the expected correct behavior?
the cli push to a repository not matching the defined Target Path
shall not display the broadcast_message.
Relevant logs and/or screenshots
on the cli pushing to another git repository
git remote -v
origin git@ssh.code.example.com:system/build-dashboard.git (fetch)
origin git@ssh.code.example.com:system/build-dashboard.git (push)
git push origin feature/pipeline-linter
Warning: Permanently added 'ssh.code.example.com,127.0.0.1' (ECDSA) to the list of known hosts.
Counting objects: 16, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (15/15), done.
Writing objects: 100% (16/16), 7.83 KiB | 890.00 KiB/s, done.
Total 16 (delta 7), reused 3 (delta 1)
remote:
remote: ========================================================================
remote:
remote: Short term = 1-3 months, Mid term = 3-6 months, Long term = 6-12
remote: months
remote:
remote: ========================================================================
remote:
remote: To create a merge request for feature/pipeline-linter, visit:
Output of checks
none
Results of GitLab environment info
none
Results of GitLab application Check
none
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)