Devin now natively supports @Github Stacked PRs ▪︎ Break down large changes into smaller, reviewable diffs ▪︎ Address and fix comments across stacks ▪︎ Automatically rebase downstream changes

Learn more about Stacked PRs in Devin:

@github I love working in stacks!!

@github No more 10k line PRs!!!

@ido_pesok @github Love this feature!!

@github So good

@github no idea why people use anything else then devin atp kek w devin

@github Devin helped make this small little meme coin over two years ago. Thanks @cognitionlabs for doing this years ago. It’s not your baby we know. The Dev is always $Devin 🤟🏼 - $Devin + AI Cultural Artifact 7gbEP2TAy5wM3TmMp5utCrRvdJ3FFqYjgN5KDpXiWPmo

@github LETS GOOOO

@github Haven't seen a Stack this good since

@github LETS GOO

@github So game changing for me

@github Does a single agent work on an entire stack or does each PR in the stack get its own subagent to work on in parallel? And how do you easily manage constant conflicts between two consecutive PRs in the stack?

GitHub moved stacked PRs to public preview today too — same day. The platform does the downstream rebase itself now: merge one layer and the rest retarget automatically. Merge queue support for stacks is the piece still rolling out over the coming weeks. So the split is GitHub handling the rebase mechanics, Devin deciding where the seams go.

@github @jaredpalmer already cookin and shipping!

@github wow didn’t know Devin had this many features fr now i feel like testing it out

@github Native stacked PR support is the kind of unglamorous feature that actually decides whether a coding agent fits into a real team workflow.

@github Stacked PRs might finally make big code reviews less painful

@github Stacked PRs decides whether an agent is usable on a real codebase. Big diffs are where review falls apart. Come on the podcast? I'd ask about the review bottleneck once agents outproduce the people checking them.

@tomasholtz @github let's go 🚀

@github @thsottiaux we needs this in Codex too

@github It keeps logging me out of my account. Also, it charged me $1000 of my real money. I can't reach support. This service is complete trash.

@github Auto rebasing downstream changes alone is worth the update

@github stacked prs would be such a game changer for my team fr

@github very nice

This project has great energy. Happy to connect 🚀

@github stacks on stacks on stacks on stacks 📈

@github Small wins for developer sanity.

@github Sent you a DM regarding a collaboration.

@github Expecting google chats integration or telegram integration 😒

@github 🔥🔥

Call me dumb, but I don't see this becoming a super-adopted feature. Every next PR depends on the previous. On review, you receive comments. If you need to change smth the first PR, it's 99% smth on a fundamental level. And now you need to change every other branch that depended on it. So the normal flow is: Get a review on the first part -> merge it to the "release branch" -> start working on the second part -> get approved -> merge to the release branch. The only way I can see this "being useful" is if you have a massive PR and you want to make the reviewer's life easier so he can see how your feature evolved over time, but the reviewer can achieve the same if he just reviews commit by commit in 1 PR. I like GitHub; I just don't get this feature...

@jaredpalmer @github How many developers inside company only work on cloud ?

@github I'm doing a profile article on your startup, feel free to share it if you like it. The Newsletter AI Supremacy.

@github YES!!!

@github Automatic rebasing is doing the heavy lifting here. Without it, five tidy PRs just become one long afternoon.