Only if you can be positive that a problem is isolated from the rest of your code base, should you even consider using a stake branch to find and fix it. Alternatively, you could have a separate Clean up old branches UI that can show fully-merged branches and how long ago their last commit was (27 days ago). Run the git-delete-merged-branches command: git-delete-merged-branches Follow the prompts to select which merged branches you want to delete. Looking for a solution to a problem in a partial reproduction of the code is likely to cause more problems than it solves. But (a) that probably isn’t true and (b) even if it was, you need to pull in all of the other changes as well that happened prior to the PR as they could be the source of your problem. To delete a remote branch, use git push origin :mybranch, assuming your remote name is. The only reason to maintain it, would be because you expect some trouble with it, and think maintaining the branch is going to be the easiest way to get back in and fix up whatever problems crop up. You can safely delete local branch with git branch -d yourbranch. 184 Community Groups Community Products Bitbucket Questions Restore merged/deleted branch in bitbucket Restore merged/deleted branch in bitbucket gmanimyl Long back I have created a pull request to merge my branch into master and it was done. Basically you need it for a good code review, but that is exactly what PR should be. The need for having an easy to access branch for looking at the history of the feature, should be wrapped up with the PR. There’s no reason to hang onto a dead branch, Everything that you need to know is now contained within master. Deleting the source branch prevents confusion as the topic branch itself doesnt have a commit merging it into the default branch. I would suggest that all PR’s be followed by a delete.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |