Versions
- 9.6
- 9.5
- 9.4
- 9.3
- 9.2
- 9.1
- 9.0
- 8.19
- 8.18
- 8.17
- 8.16
- 8.15
- 8.14
- 8.13
- 8.12
- 8.11
- 8.10
- 8.9
- 8.8
- 8.7
- 8.6
- 8.5
- 8.4
- 8.3
- 8.2
- 8.1
- 8.0
- 7.21
- 7.20
- 7.18
- 7.19
- 7.17
- 7.16
- 7.15
- 7.14
- 7.13
- 7.12
- 7.11
- 7.10
- 7.9
- 7.8
- 7.7
- 7.6
- 7.5
- 7.4
- 7.3
- 7.2
- 7.1
- 7.0
- 6.10
- 6.9
- 6.8
- 6.7
- 6.6
- 6.5
- 6.4
- 6.3
- 6.2
- 6.1
- 6.0
- 5.16
- 5.15
- 5.14
- 5.13
- 5.12
- 5.11
- 5.10
- 5.9
- 5.8
- 5.7
- 5.6
- 5.5
- 5.4
- 5.3
- 5.2
- 5.1
- 5.0
- 4.14
- 4.13
- 4.12
- 4.11
- 4.10
- 4.9
- 4.8
- 4.7
- See all
Branch permission patterns
Using branch permissions
On this page
Related content
- Pushing a branch to Bitbucket fails with the error, "refspec matches more than one".
- NoDefaultBranchException error regarding the default branch - this branch does not exist
- Understanding Diff view in Bitbucket Server
- Changing a branch caused git to "refs/heads/ refs/tags/' exited with code 128 saying: fatal missing object"
- Missing Commits in Bitbucket Server
- Missing commits in Bitbucket after a filesystem migration
- Using branch permissions
- Using branches in Bitbucket Server
- Case-sensitivity in Bitbucket server
- Controlling access to code
Bitbucket Server supports a powerful type of pattern syntax for matching branch names (similar to pattern matching in Apache Ant).
These expressions use the following wild cards:
? | Matches one character (any character except path separators) |
| Matches zero or more characters (not including path separators) |
| Matches zero or more path segments. |
Pattern used in branch permissions match against all refs pushed to Bitbucket Server (i.e. branches and tags).
In git, branch and tag names can be nested in a namespace by using directory syntax within your branch names, e.g. stable/1.1. The '**' wild card selector enables you to match arbitrary directories.
- A pattern can contain any number of wild cards.
- If the pattern ends with
/then**is automatically appended - e.g.foo/will match any branches or tags containing afoopath segment - Patterns only need to match a suffix of the fully qualified branch or tag name. Fully qualified branch names look like
refs/heads/master, while fully qualified tags look likerefs/tags/1.1.
Also see the Ant documentation.
Examples
* | Matches everything |
PROJECT-* | Matches and branch or tag named PROJECT-*, even in a name space. e.g. refs/heads/PROJECT-1234, refs/heads/stable/PROJECT-new or refs/tags/PROJECT-1.1 |
?.? | Matches any branch or tag of 2 characters separated by a '.'. e.g. refs/heads/1.1, refs/heads/stable/2.X or refs/tags/3.1 |
tags/ or tags/** | Matches all tags and any branches with 'tags' as a namespace. e.g. refs/heads/stable/tags/some_branch, refs/tags/project-1.1.0 |
heads/**/master | Matches all branches called master. e.g. refs/heads/master, refs/heads/stable/master |
Related content
- Pushing a branch to Bitbucket fails with the error, "refspec matches more than one".
- NoDefaultBranchException error regarding the default branch - this branch does not exist
- Understanding Diff view in Bitbucket Server
- Changing a branch caused git to "refs/heads/ refs/tags/' exited with code 128 saying: fatal missing object"
- Missing Commits in Bitbucket Server
- Missing commits in Bitbucket after a filesystem migration
- Using branch permissions
- Using branches in Bitbucket Server
- Case-sensitivity in Bitbucket server
- Controlling access to code