labrad/pylabrad

Remove stale branches

kunalq opened this issue · 4 comments

kunalq commented

There are quite a few stale branches. Should we establish a procedure for culling them? e.g. anything >1 year old?

https://github.com/labrad/pylabrad/branches/stale

maffoo commented

Certainly for stale branches that have been merged, we can remove those (presumably whoever merged just forgot to delete the branch at that point). I don't have too much of a problem with leaving old branches around, but it's probably good to at least ping people periodically to clean up their u/ branches.

DanielSank commented

I'd keep any branches which begin with an issue number, but ask people to nuke their u/username/whatever branches.

maffoo commented

I like @DanielSank's suggestion. We can handle the few branches that don't follow either convention on a case-by-case basis. AFAICT, that would be these:

  1. GPIB
  2. base-DeviceWrapper-on-object
  3. node-testing
  4. node-updating
  5. packetDump
  6. units_rounding_funcs
  7. vinceGPIB
kunalq commented

It's unfortunate that we can't get stats on the last time a branch was "used," that way at least we know if someone has an active check-out somewhere.