To elaborate on what Dan said: What has happened is that your local record of the remote references has 400+ remote branch references. Some time ago, I raised the same concern that you have here, and we got that number down to a couple dozen. But your local references are still there.
git fetch origin will update your local references to your remotes, and the --prune option on that command will remove any local references that are no longer on the remote. For what it's worth, we do seem to have a handful of branches that are still getting pushed to origin for the sake of PRs, etc. While remembering to delete your branches after the PR gets merged is well and good, I'd take it one step farther and encourage everyone to not sully the common space with their work-in-progress or PR branches. That's exactly what a fork is for. And then we don't get into this case of accruing extra references on origin in the first place. Imagination is Change. ~Patrick On Thu, Apr 18, 2019 at 8:46 AM Dan Smith <dsm...@pivotal.io> wrote: > You just need to do git remote prune origin. Git doesn't remove remote > branches from your local copy automatically. > > -Dan > > On Thu, Apr 18, 2019 at 8:08 AM Bruce Schuchardt <bschucha...@pivotal.io> > wrote: > > > Sorry to spam everyone. "git branch -r" seems to be a local thing. I > > made a fresh clone of the apache repo and now only see the branches > > mentioned in the UI. > > > > On 4/17/19 5:06 PM, Jason Huynh wrote: > > > Hi Bruce, > > > > > > I am unable to see the same branches on geode repo. I do see these > > > branches on my personal fork but that's because I haven't updated my > own > > > personal fork in some time... > > > > > > Is there a chance that your origin is pointing to your personal fork > and > > > not the Apache Geode Repo? > > > > > > I am also unable to see these branches through the ui: > > > https://github.com/apache/geode/branches/all > > > > > > > > > > > > On Wed, Apr 17, 2019 at 4:17 PM Bruce Schuchardt < > bschucha...@pivotal.io > > > > > > wrote: > > > > > >> We have nearly 400 branches in the repo right now. Most of them are > for > > >> efforts that have been merged to develop long ago. Don't forget to > > >> delete your branches when you're done with them. > > >> > > >> > > >> > > >