You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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