Decision 1 Branch Permissions
I suggest you first create a branch on the bitbucket server, with write permissions (this is usually done using Jira, so you can assign a task ID to the branch).
To handle branches and permissions check this guide . You can define a template with the appropriate permissions so that certain branches automatically apply these properties.
Then the user will do
$ git fetch origin $ git checkout feature/taskID-whatever
After development, he will be able to push a branch and execute a stretch request in order to develop.
$ git push origin feature/taskID-whatever
Develop only need to read, but not branches.
Solution 2 Use fork
In the same tutorial that you follow, you will find how to fork . This way your developer will have a clone in his own bitbucket repository.
source share