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
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.