https://twitch.tv/ThePrimeagen - I Stream on Twitch

https://twitter.com/terminaldotshop - Want to order coffee over SSH?
ssh terminal.shop

### Sources
* https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish 

* https://news.ycombinator.com/item?id=47881672&utm_source=trunk-io&utm_content=%2Fblog%2Fwhat-happens-if-a-merge-queue-builds-on-the-wrong-commit 

* https://x.com/ThePrimeagen/status/2048033949864051173/photo/1 

* https://damrnelson.github.io/github-historical-uptime/?utm_source=chatgpt.com

* https://trunk.io/blog/what-happens-if-a-merge-queue-builds-on-the-wrong-commit

* https://www.githubstatus.com/

* https://www.youtube.com/watch?v=8fcSviC7cRM

Primeagen's resource offers insights, tutorials, and resources for software developers and technology enthusiasts. Readers can learn about productivity hacks, career development strategies, and personal growth. With articles, videos, and practical advice, Primeagen provides  guidance and expertise for achieving professional success and fulfillment.

ThePrimeTime

GitHub's merge queue had a serious regression on April 23rd where squash/rebase commits were generated from the wrong base state, causing thousands of lines of already-shipped code to be silently removed from main branches. PRs appeared correct in the UI but what actually landed on main was completely different — in one example, a +29/-34 diff became a +245/-1,137 commit. The bug affected an unknown number of repositories, with GitHub citing 2,800 affected PRs out of 4 million merged, though some companies reported hundreds of affected PRs on their own. The incident raises questions about whether GitHub uses force pushes internally, why the status page showed no outage, and whether a full postmortem will ever be published.

This Bug