You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
A third possible category is any branches undergoing active development but for which no PR has yet been made. I know of none in this category, but it's possible. @jsha?
Activity
Hainish commentedon Oct 11, 2016
Sounds reasonable to me - I've self-assigned this.
gloomy-ghost commentedon Dec 9, 2016
Any updates here? Maybe we can delete merged branches first, those have 15k+ commits behind and 0 commits ahead master.
Hainish commentedon Dec 9, 2016
There are two categories of branches we need:
1a.
master1b.
release- for https://www.eff.org/https-everywhere/atlas/2a.
https-attemptfor example, in In HTTP Nowhere mode, attempt HTTPS before block. #7435I'm not sure if we have a comprehensive list of those in (2).
Hainish commentedon Dec 9, 2016
I'm not sure of the best way to enumerate (2) except to use the GitHub API, so that's what I'll do now.
Hainish commentedon Dec 9, 2016
The only two PRs in category (2) are #7435 and #4462
I therefore propose we delete all branches other than the following:
masterreleasehsts-transformhttps-attemptIf there are no objections, I'll move forward with this on Monday
Hainish commentedon Dec 9, 2016
A third possible category is any branches undergoing active development but for which no PR has yet been made. I know of none in this category, but it's possible. @jsha?
jsha commentedon Dec 9, 2016
I don't know of any either.
Hainish commentedon Dec 9, 2016
In that case, I'll be running this to delete 91 branches on Monday:
Hainish commentedon Dec 12, 2016
Done!