Draft: POC for target branch rules
What does this MR do and why?
NOTE This is a proof of concept. Whilst it works for a set flow there is still more to be done for this and a lot of UX updates to be made.
This allows for projects to create a list of rules, like protected branches, so that when a branch matches that pattern it will target the specified branch.
What is different to the projects default branch? Well this allows for various different git flows to be used, instead of having a single branch as the default for all merge requests this will only project owners to create rules for what a branch should target.
Screenshots or screen recordings
Screen_Recording_2023-05-18_at_14.06.11
Screen_Recording_2023-05-18_at_14.07.00
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.