I have a user story in Jira called "Add Summary Operator to Calculator". From this story, I click create branch and get feature/proj09-14-add-summary-operator-to-calculator as my new branch to work with. I picked develop as the source branch.
So then after a few commits, I create a pull request, get approvals, and merge it back into develop. Maybe I manually pre-merged develop into my feature branch first, but it doesn't matter. There were no conflicts and the merge completed.
But the branch is still there because I chose not to close it. Can I continue and make more commits followed by another PR+merge, or is there something intrinsic to BitBucket that causes problems on your local working tree after attempting a double PR and merge on a single branch?
Any answers in the form of ".. it should... theoretically.." I will interpret as a NO.
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
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