Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I’m at Google, we have a million + file codebase. Every piece of code is snapshotted (no need to commit, automatic snapshot whenever a change is made). Every line of code has its own unique URL (this is for your branch too, not just overall). Background tests running nonstop hourly. Never seen any downtime. The infra at Google is insane




GitHub is a completely different scale. If Google hadn't wasted its opportunities to become the prime source code platform they'd also have issues.

That’s what I disagree with, I think Google codebase scale is massive. It has android + chrome + Google + Waymo + tensorflow etc, this is a lot of code. And also consider that every third party library is put inside Google3 codebase too, there are no truly external dependencies, all the code is there in one repo, with their version one version principle. I think Google is roughly similar scale to GitHub and is managing things far better

Without manual commits, is there any way to record the intention of each change?

Yes you can still commit as a logical delineation of changes. And every commit is automatically a PR, folding multiple commits is possible but not the common workflow, they prefer just reviewing and approving each commit.

There are manual commits, they're just called changelists.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: