Branch configuration example
Regular Expression Explanation
^(feature|bugfix|hotfix|release|develop)\/[a-z0-9][a-z0-9\-_]*$
→ The branch must follow this pattern to match:
Start with one of the allowed prefixes:
feature/
,bugfix/
,hotfix/
,release/
, ordevelop/
Followed by a lowercase alphanumeric name:
Can include lowercase letters (
a-z
), numbers (0-9
), hyphens (-
), and underscores (_
).Must start and end with a letter or number (no trailing
-
or_
).
All of the following error messages are displayed when a pull request is created and can also appear in combination.
Branch configuration in source branch
Configuration

Possible results
Commands | Expected results |
---|---|
BASH
|
→ Missing a required prefix |
BASH
|
→ Double slashes are not allowed |
BASH
|
|
Configuration

Possible results
Commands | Expected results |
---|---|
BASH
|
|
BASH
|
|
BASH
|
→ The branch matches the naming convention |
Branch configuration in destination branch
Configuration

Possible results
Commands | Expected results |
---|---|
BASH
|
→ Missing a required prefix |
BASH
|
→ Double slashes are not allowed |
BASH
|
|
Configuration

Possible results
Commands | Expected results |
---|---|
BASH
|
|
BASH
|
|
BASH
|
→ The branch matches the naming convention |