When I create a new repository in bitbucket with no branch permissions and then clone it to my local computer, I'm able to commit to my local and then push to the new remote that I made. If I change the branch permissions to only allow changes to be made to the remote repository via pull request, then I'm not able to create a pull request from my clone so that changes can be pushed to the remote. Instead I have to fork the remote repo and then clone the fork and commit to clone, push to fork, and then do pull request from fork to the remote.
My question is why can't I create a pull request from my clone and once approved push to the origin? Is it absolutely necessary to go through a fork if I require pull request.
I think I'm misunderstanding a basic priniciple of git.
Hello @Zachary Thomas ,
If you own the repo and cloned it to work locally. You will need to create a branch locally and work on the feature of your choice and then when you push the branch back online, you should be able to create a pull request to merge into the master branch. Still need clarification? Check out this tutorial on branching by the Atlassian team =>https://www.atlassian.com/git/tutorials/using-branches
Hello Sourcetree users!!! With the recent removal of Bitbucket Cloud account passwords for app passwords (please see our Bitbucket Cloud community post for details on why we made this change for se...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events