LINKED LIST [txt mode] ▸ Keeping master green at scale
home explore | log in

Keeping master green at scale

eng.uber.com · first added by @afreshcup · 2026-09-30 · 1 upvotes

log in to save, upvote or flag this.


─── In 0 lists ─────────────────────────────────────────

(not in any lists yet)

* If a Build Takes 4 hours, Run It Every 4 Hours (from the discussion)
* Successfully Merging the Work of 1000+ Developers (from the discussion)

─── Discussions ────────────────────────────────────────

* Keeping master green at scale
301 pts · 115 comments · node

─── From the discussion ────────────────────────────────

* Advantages of monolithic version control
danluu.com · node
* Keeping master green at scale
blog.acolyer.org · node
* CppCon 2017: Titus Winters “C++ as a "Live at Head" Language”
youtube.com · node
* Watchman - A file watching service | Watchman
facebook.github.io · node
* GitHub - smarkets/marge-bot: A merge-bot for GitLab
github.com · node