Determine why mozilla/mozilla-central has been removed from service by GitHub
bugzilla.mozilla.org
Determine why mozilla/mozilla-central has been removed from service by GitHub
1–9 of 9 posts
Re: Determine why mozilla/mozilla-central has been removed from service by GitHub
#2Re: Determine why mozilla/mozilla-central has been removed from service by GitHub
#3Misleading title a little - the repos were disabled due to file system issues.
Interestingly, the initial email reported the cause to be a ToS violation.
Re: Determine why mozilla/mozilla-central has been removed from service by GitHub
#4(Don't forget, mozilla-central has more commits than GitHub can even count (they call it "10k+"), hundreds of forks, a few dozen commits a day, etc.. so it's atypical)
Re: Determine why mozilla/mozilla-central has been removed from service by GitHub
#5Dunno if its really news?
Re: Determine why mozilla/mozilla-central has been removed from service by GitHub
#6Misleading title a little - the repos were disabled due to file system issues.
(Assuming the title hasn't been changed…) Removed from service isn't the same as disabled? To my mind they're synonymous. But I suppose the former may sound a little more inflammatory. Interestingly, the initial email reported the cause to be a ToS violation.
Re: Determine why mozilla/mozilla-central has been removed from service by GitHub
#7Re: Determine why mozilla/mozilla-central has been removed from service by GitHub
#8Seems like did a merge that somehow broke GitHub, and it's back to normal now. (Don't forget, mozilla-central has more commits than GitHub can even count (they call it "10k+"), hundreds of forks, a few dozen commits a day, etc.. so it's atypical)
Re: Determine why mozilla/mozilla-central has been removed from service by GitHub
#9Seems like did a merge that somehow broke GitHub, and it's back to normal now. (Don't forget, mozilla-central has more commits than GitHub can even count (they call it "10k+"), hundreds of forks, a few dozen commits a day, etc.. so it's atypical)
That's pretty standard for a private repo.
This sounds like someone pushed the old shas into the new
shas in some repo, which would be a ~1.5million commit push.