Make remote branches easier to manage (perhaps, redefine git d-)

[salcode]

Now that we've added

git delete-remote-tracking-branch <local branch name>

in #65, which makes it easy to delete a remote tracking branch based on a local branch name, we should look at other ways to make it easier to manage remote branches.

Current we have

git d-

defined as deleting the previous local branch (from #56). This is helpful for after we merge a feature. Since we generally want to remove the remote tracking branch as well, I'm wondering if we should redefine git d-.

Specifically, I'm wondering if git d- (or some other new command) should both:

• delete the remote tracking branch associated with the previous branch
• delete the local previous branch

There is some discussion of this idea in this comment on 65 and redefining git d- goes against the thoughts in that comment. However, I think it is worth reconsidering and making a major version jump on this project (e.g. 1.3.0 to 2.0.0) since this would be a breaking change.

[salcode]

While adding

git delete-remote-tracking-branch <local branch name>

in #65 seems like the solution to removing a remote branch I am coming across the situation where there is no tracking branch even though I've pushed my local branch to origin.

I'm not sure if this is an issue with determining the remote tracking branch or it is really isn't set.

Perhaps, we should also try to delete a branch from origin that has the same name as the current branch.