Re: [PATCH] branch: introduce --(no-)has-upstream and --(no-)gone options

[Konstantin Khomoutov <kostix@bswap.ru>]

Alex Henrie <alexhenrie24@gmail.com> writes:

> GitHub and GitLab have features to create a branch using the web
> interface, then delete the branch after it is merged. That results in a
> lot of "gone" branches in my local clone, and I frequently find myself
> typing `git branch -v | grep gone`. I don't want `git branch --merged`
> because that would include branches that have been created for future
> work but do not yet have any commits.

Possibly a rather silly remark, but you could make a habit of periodically
running

  git remote prune <remotename>

or fetching with "--prune".

At my $dayjob, we use GitLab, and I routinely fetch with "--prune" because
most of the time there's no sense in seeing stale (merged in and deleted)
branches, and if it's really needed, their then-tips can be figured out from
the merged commits which have integrated those branches.