If a user create a write restriction for a pattern with wildcard, the user also can't create new branches that match the pattern. Example, if a user creates a restriction for "release/*", the user will never be able to create any branches under "release/"
A user should be able to do so for a few reasons - do review this use case by a user:
Our project are currently using gitflow. There are 5 kind of branches: release/, hotfix/, dev, master and feature/*. What we want is to prevent all changes without Pull Request > for master, hotfix, release, dev branches.
We have used Branch Permission to setup rules to require changes must be merged via Pull Request and prevent pushing changes directly to master, hotfix, release, dev. Because we don't allow changes to push directly, we also can't create new release and hotfix branches. But as the gitflow, before any release or hotfix we have to create those kind of branches.
There is a solution that is to create only one release and hotfix branched and every time > we change master, we have to create a Pull Request to merge that change to that release and hotfix. But that is not standard of gitflow and it also causes our process become more complicated.