Hey folks,
This is an update to: https://sh.itjust.works/post/580838
On https://github.com/csm10495/commit-ment, I made it to somewhere around 22 million commits. I can't imagine this is not a world record for commits to a single branch. In the middle of the night, I got an email from GitHub support saying:
A few minutes later, I got another email like so:
I've asked them if the two emails are related (and I guess if the first one is some sort of error since there was no personal info in that repo). I've also asked if they can give any information about what triggered the email and if they can give me more info about what it looks look on their side.
I've also asked if they can re-enable it so I can give one more commit to say the final results on the readme then (public) archive it.
We'll see what they say.
Doing a pull is interesting at the moment, it shows:
git pull origin master --no-rebase -vvv
ERROR: Access to this repository has been disabled by GitHub staff due to
excessive resource use. Please contact support via
https://support.github.com/contact to restore access to this repository.
Read about how to decrease the size of your repository:
https://docs.github.com/articles/what-is-my-disk-quota
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Similar thing happens if you try to clone: git@github.com:csm10495/commit-ment.git
So yeah, I figured this would happen sooner or later. I just hope they can tell me a bit more about what it looks like on their side since managing this repo on my box is a pain, I can't imagine what it could look like on theirs. I'm also curious how pull requests could merge at such a rate given that just doing a pull on my end could take minutes. So many questions!
This whole project was really just for curiosity on my end, so anything I can learn/find out is much appreciated on all ends.
Anyways, just figured I'd update y'all.
You must log in or # to comment.
Congrats on becoming the reason a non trivial rate like is going to be imposed 😆
That’s hilarious! I’m actually impressed it lasted for 22 million commits, I would have thought the breaking point would be earlier.
I think this means you win
Tiny mini update: GitHub support has been really nice and all is fine. They told me that this repo was taking up 5.5TB of resources doing certain operations. Also pointed me to https://github.com/github/git-sizer and https://github.blog/2018-03-05-measuring-the-many-sizes-of-a-git-repository/
They are happy to have the 5.5TB back… and I’m happy to give them back. I’ll probably upload/archive the code and the final notes in a new repo, and then close this chapter.
If I ever really want to play with this again, I’d get a GitHub Enterprise license and let it go wild on a local box.
I think it’s a interesting case that they didn’t expect somehow, I have a real repo that has around 1.5M commits on GHEC and surprisingly it works rather well so far, although some functionality (that I don’t really care about) is slower than usual.
Hello HN! OP, you’ve reached the front page of Hacker News:
I wonder if this is a sign that Lemmy has achieved real Reddit replacement status. HN occasionally links to some interesting Reddit post like it did here for Lemmy
