Arjay McCandless
Region: US
Saturday 01 August 2026 20:25:11 GMT
125989
6913
153
614
Music
Download
Comments
ItsRed :
Just use subbranches and merge changes down? 😅 Never had issues with that
2026-08-03 02:56:49
1
ステファノ (Stefano) :
If I stack my 50 prs and the first one gets rejected, do I need to re-do the other 49 based on the initial one?
2026-08-03 01:24:04
1
wut :
Band-Aid on a bullet wound when it comes to AI slop.
2026-08-02 22:27:30
1
louis :
I'm so confused cause you can already do this by branching off your previous pr, setting that branch as the base branch, and turning on deleting of head branches on merge 😅😅😅😅
2026-08-01 21:24:05
352
That guy 🤷🏻♂️ :
I mean you can already essentially do this? Just branch off of one PR branch and start the next task
2026-08-02 02:56:00
49
pollito :
Waiting for my PR review is literally my free time. Don’t mess with it
2026-08-02 19:18:56
0
upfkd :
this is basic git?
2026-08-02 18:53:56
0
feranmi :
I still don't understand how this is revolutionary, I've been stacking p.rs on github/gitlab for 4 years by pointing sub branches to each other, or is this different?
2026-08-01 21:24:19
130
Aaron Cowie :
PR reviews are a waste of time
2026-08-01 23:08:24
5
Mpho :
Cascaded pr's have been existing forever
2026-08-02 09:02:11
0
2K :
Fix for a poor project and team management. If you wait too long for a review maybe a PR is too big? Or maybe the dev culture is not as it should be? Fix the root cause, not adapt.
2026-08-02 08:55:07
6
user8121616439376 :
They need to fix how these work with squashed merges. It creates false merge conflicts which require forced pushes.
2026-08-02 00:03:00
0
Johan :
Yeah still not a big fan of this, if we want to split one big pr into chunks we can still use different commits, this is only one more layer(commit->pr->stacked pr)
2026-08-01 20:30:11
5
Chris :
couple of days for an MR? nah thats the first fault
2026-08-02 12:15:41
0
SterlingToffeeTime :
Whenever I get tagged to review a stacked PR, I know I’m in for a horrible time.
2026-08-01 22:27:39
13
ViLsonCake :
As the author mentioned, usually I just create a new PR to merge to the feature branch of the previous PR instead of main to see only new changes, once first PR is merged you change the branch to merge to main and that’s it.
2026-08-01 20:34:28
41
lemon :
I feel like this just makes more work for the person reviewing the PR
2026-08-02 00:51:15
5
gulkaran :
Been using Graphite at work for a long time and stacks are a game changer esp in monorepos but it takes a while for folks to get used to it. You iterate quicker, your reviews are smaller, PRs are more atomic, and AI performs better. You can clear context and work slice by slice rather than one larger PR where context rot becomes an issue. I don’t see how I could ever go back to stackless
2026-08-01 21:12:07
6
Michael Bleterman :
they invented branches and merge???
2026-08-02 02:56:17
6
user1317 :
how is this different from stacked branches? no conflicts to resolve?
2026-08-02 19:41:51
0
Matandk :
You can literally merge the latest commits to your branch from main and your changes will still be in place lol
2026-08-02 22:14:18
3
user19dmaw6fv6 :
Stacking PRs from a security standpoint is a nightmare
2026-08-02 10:12:53
0
FJ Scents :
Tbh rebasing solves a lot of this lmao
2026-08-01 23:38:25
0
nickname :
good luck in your third PR where you used changes from unmerged PR1, and then someone requesting changes on PR1. causing to rewrite whole PR3
2026-08-02 21:18:55
3
𝕸𝖆𝖌𝖎𝖘𝖙𝖊𝖗💀 :
I think that it is an amazing feature we were lacking for quite a long time 😎
2026-08-02 04:13:33
3
To see more videos from user @arjay_mccandless, please go to the Tikwm
homepage.
