-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chore: delete all branches that have been merged into main #3602
Comments
Deleted all of those apart from |
Don't know if you want to close the issue or keep it open and badger @iadawn about the similar trawl you suggested. |
@fstrr wow, I forgot I filed this. great stuff. doing a fresh trawl, there's a few more now:
|
Gone! There are a lot of branches that look like they can be deleted—the earliest are from 2018. If you run this command (thanks, ChatGPT), you get a list of all the remotes in the date order they were last committed to:
|
Well, |
Removed some more from that table above, so we're down to 247 branches now. Will maybe talk this through at tomorrow's backlog meeting. |
Given that #3878 leads with a remark about continuing this, and given that I just did another pass today to delete merged branches, I imagine we ought to close this. (FWIW, as of right now there are 125 branches total including protected branches, so I'd say we've made a dent) |
github says there's 124 (?) branches and 125 pull requests, so it definitely looks like we've made good progress removing any hanging/left-over branches at least. great stuff. |
There are currently 305 branches on this repository. Among those, there are many that are hanging around after being merged ages ago. Running a naive
git branch -r --merged main | grep -v "main"
gives the following list:While it's only a drop in the ocean, suggest at some point doing a similar trawl and removing stale/unused branches (checking though if some branches have been merged, but are then still being worked on)
There are no doubt many other branches that belong to issues/PRs that have since been closed without merging, and possibly the command-line shenanigans above may not catch branches that were originally merged into
master
when that was the default name, or merged into another branch that then was merged intomain
... but it might be a start./cc @iadawn
The text was updated successfully, but these errors were encountered: