<!--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=237884) </details> <!--IssueSummary end--> ### Problem to solve As a developer, when my branch name does not match the specified regular expression, I would like the attempted branch name in the error message so I can quickly resolve my errors. ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) * [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager) * [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test) ### User experience goal The user should be able to quickly resolve branch name errors. ### Proposal When a branch name does not conform to the specified regular expression, include the attempted branch name in the error message. Example error message for a cherry-picked branch name: > Branch name (`feat/X~ te$t !*`) does not follow the pattern '^((feature|personal)(-[a-z0-9]+){2,}|development|(cherry\-pick\-[a-z0-9]+))$' ### Further details <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. --> ### Permissions and Security ### Documentation ### Availability & Testing ### What does success look like, and how can we measure that? ### What is the type of buyer? ### Is this a cross-stage feature? ### Links / references <!-- Label reminders - you should have one of each of the following labels if you can figure out the correct ones -->