this post was submitted on 30 Jun 2023
46 points (97.9% liked)

Git

2920 readers
1 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
46
Possible World Record: Most commits to main branch on GitHub (github.com)
submitted 1 year ago* (last edited 1 year ago) by csm10495 to c/[email protected]
13 comments fedilink hide all child comments
 

I decided to see how many commits GitHub (and git) could take before acting kind of wonky. At ~19 million commits (and counting) to master: it's wonky.

The GitHub API has periodic issues merging/creating PRs. (I use PRs since that is more reliable than keeping a local master up to date via pulling at this point).

GitHub reports... infinity infinity commits. Doing a full clone from GitHub Actions is taking around 2 hours.

Using:

git pull origin master

to update my local master hangs for a while before even printing anything.

If anyone has seen a public GitHub repo with more commits to its main branch, let me know.

If anyone wants to see how slow wonky git acts at this scale, feel free to clone.

Edit: Update to this post is: https://sh.itjust.works/post/672069

top 13 comments
sorted by: hot top controversial new old
[–] [email protected] 31 points 1 year ago

Was this you? 🫀

[–] [email protected] 12 points 1 year ago (1 children)

Some people just want to see the world burn. Haha.

[–] [email protected] 7 points 1 year ago (1 children)

It feels like it's radiating chaotic energy for the sake of learning and I'm a fan

[–] [email protected] 6 points 1 year ago

I love it.

These are the types of people to find something "Huh, that's a weird reaction"

[–] [email protected] 8 points 1 year ago (2 children)

So what's next?

[–] csm10495 6 points 1 year ago

Part of me wants to try to look into the git cli to try to see why some of the hangs happen. I don't think any sort of hang with no output (at least with -v) should happen normally.

Who knows if I'll get to that point.

Otherwise I'll let it just keep committing.

[–] [email protected] 7 points 1 year ago

This might be good to cross post to [email protected] ... 😱

[–] [email protected] 4 points 1 year ago

I wonder if the size of the commits also plays a role.
The latests commits are just an index being incremented, it'd be interesting to update the script to replace and commit lorem impsum text (maybe two or three paragraphs would be a good base)

[–] [email protected] 1 points 1 year ago (1 children)

Infinity commits is interesting. Do you think it's caused by GitHub trying to count commits and timing out?

[–] csm10495 3 points 1 year ago (1 children)

At this point I think so. Even the API (v3 or graphql) can't get me a commit count anymore. It usually gives something like a 503 with a reference id to give support.

Needless to say, I don't think its worth bugging support about it :P

[–] [email protected] 1 points 1 year ago (1 children)

It might be worth it. Not sure their systems have been stressed in this way before and they might want some engineers to look at it. It could lead to some more efficencies in smaller repos. Or it could lead to nothing. Might be worth contacting them to see. Even if you ultimately don't care about this repo.

[–] csm10495 1 points 1 year ago

Fair enough. I created a thread on the support forum. Since I don't have a paid account, I can't contact support directly.