Clean up stale branches
krOoze opened this issue · 8 comments
Please consider cleaning up stale branches in this repo.
- It is cumbersome to switch to the relevant branches (master, sdk-1.0.X, ...).
- Or discover potentially useful branches.
- Cmdline tools would give more useful output (
git branch -r) - ?
+1
@krOoze, I deleted about a hundred or so. Planning to leave this open for about a week or so. Feel free to gently call out offenders directly.
Eyeing it, most branches seem to be @tobine , @lenny-lunarg and @cnorthrop . Gentlemen, would you kindly start chipping those branches?
(Note to self: 188 b at the time of writing)
I deleted a bunch of them through the Github interface earlier, I think they are gone now.
I just deleted most of my branches. I left a couple that I still want, but that's only three. It looks we're down to 95 branches at this point.
Wow, @krOoze, this worked like a champ and I was surprised at the results. Don't see any egregious offenders any more, but will keep cleaning. Closing for now -- thanks!
@mark-lunarg Great!
Let's see... master + sdk is 20 branches, open PR is ~16 branches. So still ~60 branches that are who-knows-what.
~14 are merged PR (+ 2 are closed as merged by other means), which usually are no-brainer for delete.
And there are two pages of years old branches that apparently didn't go through the PR interface. But nobody probably knows anymore what these are...
Anyway,
is there a reason to use the mainstream repo branches for the mundane patches? Could be done in the private forks (as any of the non-members do).
Our internal CI requires the branches to be on the main repo, not downstream repos. That's why you often see us pushing branches to test PRs. We can be better at cleaning them up afterwards.