Congratulations on creating the one billionth repository on GitHub

https://github.com/AasishPokhrel/shit/issues/1

by petercooper • 1 year ago

625 126 1 year ago

bitpush• 1 year ago

curl -s https://api.github.com/repositories/1000000000 { "id": 1000000000, "node_id": "R_kgDOO5rKAA", "name": "shit", "full_name": "AasishPokhrel/shit" }

samgranieri• 1 year ago

Well shit!

mistersquid• 1 year ago

Is this what folks mean by enshittification?

arcanemachiner• 1 year ago

For anyone wondering, the name of the repo is literally "shit".

Cyphase• 1 year ago

I'm wondering if AasishPokhrel created this repo for the purpose of being the billionth.

joshdavham2• 1 year ago

I highly doubt it, but that does sound possible.

paxys2• 1 year ago

It's pretty easy to game this. Just keep creating repos till you hit # one billion and remove the old ones. Their API makes it trivial. The only issue will be rate limits, and other people simultaneously creating repos, so it's a matter of luck.

recursive2• 1 year ago

I don't believe they will renumber the old ones. Also, it can't be trivial, since two people can try this, and only one can win.

GodelNumbering• 1 year ago

There was a guy who got fired from Meta for creating excessive automated diffs in pursuit of a certain magic number

maniacalhack0r• 1 year ago

AasishPokhrel made 2 repos yday - shit and yep. no activity between may 17th and june 10th.

i have no idea if its possible to calculate the rate at which repos are being created and time your repo creation to hit vanity numbers

kylehotchkiss• 1 year ago

I think he’s in university for software development in Nepal, and it’s really touching that a milestone could go so deeply into the world. Hopefully he has a big spot for this on his resume and can find a great career in development!

netsharc• 1 year ago

I don't get why this needs a big spot in his resume, and why it should lead to a great career. A company/hiring manager that thinks being lucky to hit a magic number on some system has any relevance to work, I'd rate as very insane...

notfed2• 1 year ago

I find a bit of humor in the fact that this is completely unrequited attention. There's even a chance the guy is oblivious.

fHr• 1 year ago

repo named shit LMFAO nice

joshdavham2• 1 year ago

This is actually incredible.

umanwizard• 1 year ago

On a serious note, I'm a bit surprised that GitHub makes it trivial to compute the rate at which new repositories are created. Isn't that kind of information usually a corporate secret?

raincole• 1 year ago

Is there any reason for GitHub to hide this information though? How could it be used against them?

(I understand many companies default to not expose any information unless forced otherwise.)

toast0• 1 year ago

The rate of creation is like meh, but being able to enumerate all of the repos might be problematic, following new repos and scanning them for leaked credentials could be a negative... but github may have a feed of new repos anyway?

Also, having a sequence implies at least a global lock on that sequence during repo creation. Repo creation could otherwise be a scoped lock. OTOH, it's not necessarily handled that way --- they could hand out ranges of sequences to different servers/regions and the repo id may not be actually sequential.

xboxnolifes• 1 year ago

Companies usually hide this type of information so competitors have a harder time determining if they are growing/shrinking/neutral.

cheschire2• 1 year ago

When your moat is a billion wide, you tend to walk around in your underwear a bit more I guess.

90s_dev5• 1 year ago

Excellent Diogenes quote reference.

NooneAtAll3• 1 year ago

unless you're youtube?

paulddraper• 1 year ago

You can see the rate of creation of new users too.

Which is arguably even more interesting…

beaugunderson• 1 year ago

and you can find the latest ID incredibly quickly using binary search! (I used to track a bunch of websites' growth this way)

jaynate• 1 year ago

The repo three comma club

badc0ffee• 1 year ago

Tres commas

cheschire2• 1 year ago

Commits that go like \o/ this.

opello• 1 year ago

but, tres comas; only one m :)

adsteel_• 1 year ago

I only realized last week that Tres Comas tequila is just a bottle of 1800 Reposado with a different label

9dev• 1 year ago

Sigh. You can't make that shit up. I'm sure there's a witty metaphor in there, somewhere…

8organicbits• 1 year ago

While we are doing cool GitHub repo IDs, the first is here:

https://api.github.com/repositories/1

https://github.com/mojombo/grit

mkagenius3• 1 year ago

The millionth one is "vim-scripts/nexus.vim"

The 1000th is missing.

dgellow• 1 year ago

And the first commit: https://github.com/mojombo/grit/commit/634396b2f541a9f2d58b0...

Aachen3• 1 year ago

Makes me wonder how many repositories exist in general, from all the local Forgejo and Gitlab servers. Heck, include Subversion and Mercurial and git's other friends (and foes!)

Did anyone make a search engine for these yet, so we'd be able to get an estimate by searching for the word "a" or so?

(This always seemed like the big upside of centralised GitHub to me: people can actually find your code. I've been thinking of making a search since MS bought GH but didn't think I could do the marketing aspects and so it would be a waste of effort and I never did it. Recently I was considering whether this would be worth revisiting, with the various projects I'm putting on Codeberg, but maybe someone beat me to the punch)

mdaniel2• 1 year ago

Well, based on the API enumeration mentioned in sibling comments, surely one doesn't have to estimate

https://docs.gitlab.com/api/projects/#list-all-projects (for dumb reasons it seems GL calls them Projects, not Repositories)

https://codeberg.org/api/swagger#/repository/repoGetByID (that was linked to by the Forgejo.org site, so presumably it's the same for it and Codeberg) and its friend https://gitea.com/api/swagger#/repository/repoGetByID

Heptapod is a "friendly fork" of GitLab CE so its API works the same: https://heptapod.net/pages/faq#api-hgrc

and then I'd guess one would need to index the per-project GitLab instances: Gnome, GNU (if they ever open theirs back up), whatever's going on with Savannah, probably Sourceforge, maybe sourcehut (assuming he doesn't have some political reason to block you), etc

If I won the lottery, I'd probably bankroll a sourcegraph instance (from back when they were Apache) across everything I could get my hands upon, and donate snapshots of it to the Internet Archive

progval2• 1 year ago

At Software Heritage, we listed 380M public repositories, 280M of which are on Github: https://archive.softwareheritage.org/

Repository search is pretty limited so far: only full-text search on URLs or in a small list of metadata files like package.json.

90s_dev5• 1 year ago

This is either staged,

or incredible commentary on most github repos,

having no purpose, never being realized, and even having given up dreaming.

kristopolous• 1 year ago

Honestly I think the plurality are by students, maybe even the majority.

When I was a student I had to manually set up CVS pserver and CVSWeb to collaborate with other students on assignments.

This is a bit easier by at least a few orders of magnitude.

MindTheAbstract• 1 year ago

I really hope it's the latter, that would be quite brilliant

90s_dev5• 1 year ago

I don't mean intentionally.

I mean maybe he made that repo because he'd given up on his coding dreams. Almost.

That would be some interesting accidental meta commentary on the state of things.

extraduder_ire• 1 year ago

I think, by design, every commit in git is staged.

90s_dev5• 1 year ago

Wow.

caleblloyd• 1 year ago

Awesome! Only a little over a billion more to go before GitHub’s very own OpenAPI Spec can start overflowing int32 on repositories too, just like it already does for workflows run IDs!

https://github.com/github/rest-api-description/issues/4511

bartread2• 1 year ago

The company where I did my stint as CTO I turned up, noticed they were using 32-bit integers as primary keys on one of their key tables that already had 1.3 billion rows and, at the rate they were adding them, would overflow on primary key values within months… so we ran a fairly urgent project to upgrade the IDs to 64-bit to avoid the total meltdown that would have ensued otherwise.

hobs2• 1 year ago

heh, that's happened at at least 5 companies I have worked at - go to check the database, find - currency as floats, hilarious indexes, integers gonna overflow, gigantic types with nothing in them.

gchamonlive• 1 year ago

What are the challenges of such projects? How many people are usually involved? Does it incur downtimes or significant technical challenges for either the infrastructure or the codebase?

cyberax• 1 year ago

The same story happened inside Amazon.

darkwater2• 1 year ago

Lived that with a MySQL table. The best thing is that the table was eventually dismissed (long after the migration) because the whole data model around it was basically wrong.

neomantra• 1 year ago

A couple weeks ago there was some Lua community issues because LuaRocks surpassed 65,535 packages.

There was a conflict between this and the LuaRocks implementation under LuaJIT [1] [2], inflicting pain on a narrow set of users as their CI/CD pipelines and personal workflows failed.

It was resolved pretty quick, but interesting!

[1] https://github.com/luarocks/luarocks/issues/1797

[2] https://github.com/openresty/docker-openresty/issues/276

Drblessing• 1 year ago

Imagine if this was private. We would've lost out on this glorious moment.

jonplackett• 1 year ago

Holy shit, that’s amazing.

Aachen3• 1 year ago

Reminds me of the 100 millionth OpenStreetMap changeset (commit). A few people, myself included, were casually trying for it but in the end it went to someone who wasn't trying and just busy mapping Africa! Much more wholesome, seeing it with hindsight. This person was also previously nominated for an OSM award. I guess it helps that openstreetmap doesn't really allow for creating crap, because it's all live in production, and that's how the Nth commit is way more likely to be someone's random whim? Either way, a fun achievement for Github :)

In case anyone cares to read more about the OSM milestone, the official blog entry: https://blog.openstreetmap.org/2021/02/25/100-million-edits-... My write-up of changeset activity around the event: https://www.openstreetmap.org/user/LucGommans/diary/395954

chneu• 1 year ago

Your kind of comment is exactly why HN still rules. What a fun story. Thanks for sharing

Aachen3• 1 year ago

Aww, thanks! I wasn't sure if I should go off-topic this much so I'm happy to hear this!

ash_091• 1 year ago

A friend of mine spent an entire workday figuring out how to ensure he created the millionth ticket in our help desk. Not sure how he cracked it in the end but we had a little team party to celebrate the achievement.

This was probably fifteen years ago. I feel like working in tech was more fun back then.

darkwater2• 1 year ago

I wonder which is the latest ID today then...

deruta• 1 year ago

I was involved in the 99,999th and the 100,000th one in my FQA days.

We were being onboarded, they were just for demo and were promptly deleted. No one cared about the Cool Numbers.

lbeckman314• 1 year ago

https://ohshitgit.com

hyperhopper• 1 year ago

https://stevelosh.com/blog/2013/04/git-koans/

zaps• 1 year ago

Respect to GitHub for committing to the bit

Lammy• 1 year ago

check 'em https://knowyourmeme.com/memes/dubs-guy-check-em

CGamesPlay2• 1 year ago

Probably created via a script that just repeatedly checked https://api.github.com/repositories/999999999 until it showed up, and then created a new repository. Since repositories can be modified, could have even given it some buffer and created a bunch of repos, just delete the ones that don't get the right number. [append] Looking at the author's other repo created yesterday, I'm betting "yep" was supposed to be the magic number, and "shit" was an admission of missing the mark.

Does anyone remember D666666 from Facebook? It was a massive codemod; the author used a technique similar to this one to get that particular number.

topherPedersen• 1 year ago

You solved the mystery!

notfed2• 1 year ago

Or...not. Why are you assuming this guy purposely grabbed the repo?

CGamesPlay2• 1 year ago

Mostly just to share an approach to solving the "problem" of getting memorable numbers from a pool of sequential IDs.

But given that this user doesn't have activity very often, and created two repositories as the number was getting close, it feels likely that it was deliberate. I could be wrong!

ramon156• 1 year ago

Empty repo, so yes

JKCalhoun• 1 year ago

I wish I were still at Apple. Probably most people here know that Apple uses an internal tool called "Radar" since, forever. Each "Radar" has an ID (bug #) associated with it.

Radars that were bug #1,000,000, etc. were kind of special. Unless someone screwed up (and let down the whole team) they were usually faux-Radars with lots of inside jokes, etc.

Pulling up one was enough since the Radar could reference other Radars ... and generally you would go down the rabbit hole at that point enjoying the ride.

I was a dumbass not to capture (heck, even print) a few of those when I had the opportunity.

xmprt• 1 year ago

I was a dumbass not to capture (heck, even print) a few of those when I had the opportunity.

On the other hand, given how Apple deals with confidential data, you probably wouldn't want to be caught exfiltrating internal documents however benign they are.

msarnoff• 1 year ago

#SnakesOnARadar

bjackman• 1 year ago

At Google, the monorepo VCS has monotonic IDs like this for changes. Unfortunately a few years ago when approaching some round number, the system was DOS'd by people running scripts trying to snag the ID. So now it skips IDs in the vicinity of big round numbers :(

I think there's probably a lesson in there about schema design...

almosthere• 1 year ago

facepalm

bigbuppo• 1 year ago

Aww, he renamed it from shit to historic-repo.

Sohcahtoa822• 1 year ago

The repo seems to have gotten renamed and now redirects to https://github.com/AasishPokhrel/repository/

Lame. :-(

Sohcahtoa822• 1 year ago

It was renamed back! :-D

nojs• 1 year ago

Haha, he’s renamed it from “shit” to “repository” which makes the comments less funny

lillecarl• 1 year ago

Readme still has shit in it

jonasdegendt• 1 year ago

Check 'em! Sick dubs :^)

ChoGGi• 1 year ago

That's a perfect one billion repo.

hoppp• 1 year ago

Nerd humor is funny as shit

Congratulations on creating the one billionth repository on GitHub

Related Stories