@ewhauser We just released an update to the `gh-stack` skill that cuts the size, improves accuracy, and results in less tool calls
English
Sameen Karim
509 posts
Sameen Karim
@sameenkarim
Product @github leading Stacked PRs 🥞 Previously @rockerbox, @eventable Proud @UCBerkeley dropout
New York, NY Katılım February 2012
533 Takip Edilen943 Takipçiler
2026 Yıllık Özeti
@sameenkarim hesabının Twitter yılını gör
@sameenkarim Have you looked at the skill file? It’s 10k tokens of AI slop
English
The launch of Stacked PRs is one of the biggest releases in @github history, touching almost every service we run
I wanted to share some details about how we built it and everything that went into it
Strap in folks, this is gonna be a long one 🧵
English
Sameen Karim retweetledi
github kinda cooked with stacks, 14-pr stack merged in <1 min
no need to wait for ci after every progressive merge like some kind of animal
English
Great working with @MatthewMathes11 and the @trunkio team to bring support for @github Stacked PRs to their merge queue!
Trunk@trunkio
Congrats to the @github team on launching stacked pull requests 🥞 We are happy to support them natively on day one. Now you can enqueue any PR in a stack, and the queue tests and merges the whole stack in one atomic operation. Stacked PRs are compatible with all Trunk Merge Queue features, so you still get batching, merge graphs, priority, and failure isolation.
English
@horusgoul @MaxLevene @github @cassidoo We're rolling out access to stacks gradually for repos that use merge queue - looks like there was a quirk and it got flipped on/off. Fixed that and stacks should now be enabled for the OpenPhone/web repo ✅
English
English
Since we kicked off the project at the beginning of the year, we incrementally rolled out access in waves as we built out the feature. Availability and reliability was the number one consideration so we did a _very_ gradual ramp up in both functionality and number of users. Marketing was a big bang but the rest was anything but 😅
English
Stacked PRs are a great addition to GitHub.
But it shows the difference between startups and big tech. Graphite shipped stacked PRs in 2023. Instead of shipping it in increments, GitHub did a big bang release so that it works with all their features out of the box.
Sameen Karim@sameenkarim
The launch of Stacked PRs is one of the biggest releases in @github history, touching almost every service we run I wanted to share some details about how we built it and everything that went into it Strap in folks, this is gonna be a long one 🧵
English
Sameen Karim retweetledi
Large changes are hard to review. Smaller pull requests make them easier to ship.
Stacked PRs are now on GitHub.
docs.github.com/en/pull-reques…
English
Sameen Karim retweetledi
Blaming agents for giant PRs is like blaming calculators for bad math.
Past ~400 lines, reviewers stop reviewing and start skimming. That's been true forever.
The fix isn't smaller diffs, it's better shape. One review decision per layer.
That's what stacked PRs are for: mainbranch.dev/articles/stack…
Gergely Orosz@GergelyOrosz
Look, better late than never to ship stacked PRs. But this feature was extremely useful 2015-2025 at most companies using it. Since ~Nov 2025 when AI models became more capable and write more and more of the code, stacked diffs have so much less relevance. GH feels years behind
English
@jacobgold Thank you! We owe a lot to you and the Graphite team for paving the way and popularizing stacks 🫡 Huge respect to what you all have built and excited to see what you are cooking up next
English
@sameenkarim really enjoyed reading this thread! you guys crushed it. implementing this from the outside was certainly easier in some ways and likely much harder in others.
stoked to read all the deep dives
English
@sharoonthomas @github Yup, the plan is to support a stack contained in a single fork. So contributors can open a stack from their fork, targeting the base repo
#issuecomment-4268914593" target="_blank" rel="nofollow noopener">github.com/github/gh-stac…
English
@sameenkarim @github Thank you for shipping this capability.
Are there plans to support stacked PRs with pull requests from forks?
English
We looked at a bunch of stacking tools (phabricator, gerrit, graphite, sapling, git town, ghstack, etc.) and asked folks what they liked best about them. The Graphite team built an incredible product and defined a strong model for stacks
We have more to improve with the gh stack CLI, this is only the start
English
It's interesting - the @github stacked PRs CLI extension is _very_ Graphite inspired. Like you go up and down the stack checking out PRs, then if you amend something, you need to manually rebase the upstack.
I forget how awkward this is, because @gitbutler does all of this automatically.
English
my first PR has now been merged
first code written by a 14 year old for Ramp?
Michael Goldstein@mlg27_
excited to join Ramp as the youngest intern for the next 2 weeks! already made my first PR 👀
English
@CalvinGrunewald @depoll Yes would love to chat, will DM! I think it's definitely use-case dependent and not all tasks are well-suited for stacks. I've seen agents without guidance take a simple task and break it up into unnecessary layers. imo stacks also really shines in monorepo environments
English
@depoll @sameenkarim Would love to dig in with you guys. We are close with Vlad as well. DMs are open or you can send me an email.
English
Exciting day! 🥞 Stacked PRs are in public preview on GitHub, built by my team with many partner teams helping across surfaces: github.blog/changelog/2026…
English
@chacon Ah yup agents are always using jq to parse from the json. It was actually intended as a debugging tool (`gh stack` stores all its local state in a json file) and then I saw my agents using it 🥲
Will need to think about how we should format stack data in markdown. Thanks!
English
@sameenkarim This is super interesting. We did a lot of testing and eval loops around this and found that agents actually don’t like json. They prefer markdowny type output. If they get json, they then write perl scripts or jq to parse out the values they want.
English
P.S. Glad to still have a job after the 🥞 stunt in the navbar lol
x.com/anelgarhy/stat…
Anas@anelgarhy
thought it was called the "hamburger menu" not the pancake menu, @github explain yourself
English
That was a very long thread 😮💨 Thank you for making it this far if you're still reading.
Behind all the sizzle, I wanted to show what goes into such a big release like this.
Thank you to everyone who asked for this for years. It shipped because you kept pushing.
Lots more to come! Happy stacking 🥞
github.blog/changelog/2026…
English
@sameenkarim karşılaştırmaları
@ewhauser vs @sameenkarim @github vs @sameenkarim @matthewmathes11 vs @sameenkarim @sameenkarim vs @trunkio @horusgoul vs @sameenkarim @maxlevene vs @sameenkarim
Kendi karşılaştırmanı oluştur 
