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.
Hi @Bill Durksen ,
welcome to the Atlassian Community!
Yes, you can continue and make more commits followed by another PR + merge.
It even makes more sense to me to continue, than create a new branch.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.