Resolve "Backend: CI merge request pipelines don't start if remote branch matches a protected branch pattern"
What does this MR do and why?
Right now, we have the problem that if there is a fork project that has a branch name that matches the branch protection of the parent project, no merge request pipeline is created.
This is because we never checked if the branch protection rule equals just the parent project. Instead we checked it for all project which can lead to no merge request pipeline being created. The abilities file returns false for this case.
We changed this behavior so that it is always allowed to create a merge request event and the according pipeline from a fork.
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Related to #378945 (closed)