Configuration
...
Pull Request Please allows to protect Git branch and tag references from pushes without a pull request through the following two options:
- Specific Git refs: e.g.
refs/heads/master
This option can be used to restrict access to a fixed set of Git refs with specific values. If you e.g. use the Gitflow workflow for your repository, you can restrict access to the branchesrefs/heads/masterandrefs/heads/develop
Patterns for Git refs: e.g.
tags/**,?.?,heads/**/master
Use this option if you want to restrict access to Git refs with branches that can evolve over time. E.g. if you use the Gitflow workflow, one example might bereleases/**orrelease-*which means that nobody is able to push to a release branch (e.g.,refs/heads/releases/1.0orrefs/heads/release-1.0) anymore without a valid pull request. The syntax for these patterns is exactly the same as Stash is Bitbucket Server is using for its branch permissions page which is similar to the pattern matching known from Apache Ant. The allowed wildcard expressions are:
?
Matches one character (any character except path separators '/')
*Matches zero or more characters (not including path separators)
**Matches zero or more path segments (e.g.
**/tagsmatchesrefs/heads/tags)See here for details: https://confluence.atlassian.com/display/STASH030/Branch+permission+patterns
...
After its configuration, Pull Request Please will verify pushes to the specified Git refs and abort a push with the configured hook message whenever a user tries to push without a pull request :
