Thoughts on the "branch <b> is not fully merged" error of "git-branch -d"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I frequently get this error when trying to delete a branch that was
merged on github, and the remote branch was deleted through github's UI too.

When I then fetch and see that "git branch -v" shows it as "[gone]"), I
will want to delete it, but at that time it is pretty random which
branch I happen to have checked out. If it's some other unrelated branch
that I didn't rebase onto origin/main yet, or if it is main but I didn't
pull yet, then I get the error; but if I'm on main and I have pulled, or
I'm on an unrelated branch and I have rebased onto origin/main, then I
don't.

This feels arbitrary to me. It would seem more useful to me if the error
only appeared if the branch is not contained in any of my local or
remote branches, because only then do I lose commits. Any thoughts on that?

-Stefan




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux