Docs: feature now named "target branch workflow"
What does this MR do and why?
There's been some confusion around target branch rules (link to doc) and whether or not they provide enforcement of some kind of workflow. as posted from slack: https://gitlab.slack.com/archives/CETG54GQ0/p1702008753640199
We should not only remove "Rules" from the name but also replace it with a term that better reflects its intended function from the name of the feature in the UI and documentation.
Read more here: #434855 (comment 1693796394)
Must be merged after: !139738 (merged)
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
Go to project > settings > Merge requests
Scroll down to Target branch rules it should now be called Merge request branch workflow
Follow this workflow to create your merge request branch target and see if all screens have the right feature naming convention
- Title: Merge request branch workflow
- Field 1: Branch name pattern
- Field 2: Target branch