Issue Summary

Currently, when setting up branch restrictions at the project level and managing changes to the "master" branch, if you create a new repository and set the default branch name as "master", the repository is created without that branch. This happens with any branch name configured in the branch restrictions.

Steps to Reproduce

1. Create a project;
2. Configure a branch restriction on this project by limiting writing on the "master" branch using the "Only specific people or groups have write access" option, without adding any individuals or groups.
3. Create a new repository within this project and name the default branch as "master". Include the README and .gitignore files.
4. The repository will be created without any branch.

Expected Results

The branch restriction settings are being ignored during the creation of a repository.

Actual Results

The repository is created but without the default branch.

Workaround

Add one of the Workspace/Project Admins in the branch restriction list. This will grant them write permission on the branch, allowing them to create repositories without encountering this problem.