<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=502579) </details> <!--IssueSummary end--> The old flow for protected branches allowed to: * protect a branch that does not yet exist * display a protection rule for a branch that has been deleted Giving the nature of the new flow, we should mark the rule for a non-existing branch both on the list of branch rules and on the details page. We should handle creating a wildcard rule from a given string, if a branch of that name does not yet exist (see the screenshots below). ### Old flow for protecting a branch #### protect a branch that does not yet exist | step | screenshot | | ------ | ------ | | entering a name of a branch that doesn't exist prompts to set a wildcard of that exact string |  | | a protection rule is displayed with a note |  | #### display a protection rule for a branch that has been deleted | step | screenshot | | ------ | ------ | | creating a rule for `logs` branch that exists at this point |  | | [on Branches listing] deleting the branch |  | | [on Branches listing] confirming the action |  | | a protection rule is displayed with a note |  |