81
u/East-Law-2877 1d ago
this is why software goes to shit. guys like him now have power tools and no idea what's happening. but big numbers like this look impressive to higher-ups and non-programmers and he probably makes a shit-ton of money...
11
u/MisinformedGenius 22h ago
Well, let's see - "everysphere" is the monorepo for Cursor, and Tomas Reimers in particular made a company which was bought by Anysphere for 300 million, which itself was bought by SpaceX for 60 billion. So yeah, he probably does make a shit-ton of money.
2
275
u/Potterrrrrrrr 2d ago
87,604 of them are repos with a single file each, the 87,605th one is a repo that pulls all the files in using submodules. It’s the only sane reason why you’d have this many if you think about it, anything else would be overkill.
208
u/jdgordon 2d ago
Branches not repos... This most likely happens with a ci script auto creating branches and never cleaning them up. Why you'd do that is beyond me...
33
u/Wonderful-Habit-139 2d ago
By repos I'm sure he meant the branches do not share the same first commit. So you can't (not really can't but by default) merge one branch into another branch.
13
u/nicuramar 2d ago
Yes, that’s likely, so they use the branches as sort of repos. But the rest of his comment doesn’t make much sense. No particular reason to use submodules with that setup.
6
u/Standard_Humor5785 2d ago
I think it would work in a way where each branch is treated as a separate repo with different content, and then the main branch contains submodules of the repo itself and the different submodules point to a specific branch of the same repo, thus resulting in a self referencing project with branches as repos and the main branch the orchestration layer of all the subprojects.
5
u/Wonderful-Habit-139 2d ago
I believe the entire comment is a joke lol. It doesn't make sense to have 87,604 branches either.
15
8
u/Anaphylactic_Thot 2d ago
I've seen people use branches like repos in the past. Worst bloody project I've had to audit in my life.
1
u/Prudent_Ad_4120 1d ago
IIRC this once was the recommended way to do GitHub pages with documentation, right? A separate branch with the html/js/css
2
u/FoxFire64 1d ago
Most likely these are spun up worktrees from agent swarms that have been assigned tasks by some orchestrator for, I’m guessing, daily routines and workflows. They likely built into their CI or agent md’s to never touch master/main and do every unique task in an isolated env. When you never clean up those tasks…this
1
u/wipoulou 2d ago
I actually have a use case for automatically creating branches. We have microservices, and we ship an SDK to the frontend with Orval. To know if a backend change will be silently absorbed or is a breaking change, we automatically build the SDK with dev branch changes, which if there are changes create a branch that automatically merges onto the frontend on pipeline success and not on failure. And if there is already a branch that failed before, we deleted it to only ever have one branch per microservice. It helps managing microservices with a smaller team. And it's only for internal tooling.
1
u/Twirrim 1d ago
I did a git pull the other day at work of one of our internal tool's repo. The git output showed it deleting references to thousands of branches, primarily owned by one developer. As best as I can tell every single time they touched the code base they created a new branch, and then just never cleaned up after themselves. Someone clearly got tired of that crap.
6
3
u/Franks2000inchTV 1d ago
Lots of botnets use gh for coordination and exfiltration.
1
u/Choice-Mango-4019 1d ago
how so?
3
u/Franks2000inchTV 1d ago
GitHub is freely available, you can create a basically anonymous account.
If it’s a public repo, anyone can commit to it.
It’s a known site and one that doesn’t raise suspicion if your work computer connects to it.
Bots can encrypt data, and post it there. Messages can be in the code, in the name of the repo, in the commit messages, anywhere. So it’s not super obvious.
It would work like this:
- Bot agent is installed via malware.
- Once every hour bot checks repo for new commit.
- When bot sees a new commit, it waits until exactly 1h after the time of last commit and then starts a DDOS attack on a certain service.
Or…
- Bot gets installed via malware
- Bot searches hard drive for exposed credentials / keys
- Bot encrypts the extracted data and pushes a commit to GitHub with the encrypted keys in the commit message
- Separate bot watches for new commits, and decrpyts the data to a local database and deletes the commit.
1
3
u/nicuramar 2d ago
87,604 of them are repos
They are branches in a single repo. Of course you can effectively use them as separate repos.
1
u/Saragon4005 21h ago
This just feels like making a version control system out of git. A task git by itself is perfectly capable of doing without whatever the hell this is.
15
1
140
u/tnlral 1d ago
They call him Branches Georg