-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Consider cleaning up stale branches #488
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
Comments
I've asked folks to clear out their stale branches, so it should get a bit better today. Thanks! |
Cleared out a lot of branches so far, still some more to go. |
Closing this issue for now because we've removed most of the dead branches. I'm still working on getting folks to delete any other unneeded branches. |
Indeed, it's starting to look well. Thanks! |
natemcmaster
pushed a commit
that referenced
this issue
Nov 22, 2018
…master [automated] Merge branch 'release/2.2' => 'master'
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are currently a lot of stale branches in each of the aspnet projects that clutter the list on the Github page or when listing with
git branch -a
. It would be great if the merged/closed/forgotten ones would vanish.The text was updated successfully, but these errors were encountered: