hey folks 👋 i often work with pretty deep stacks (25+ prs) and sometimes the top portion is conceptually a brand new feature that just happens to depend on all the foundational work below it. i wonder if theres a way of "splitting" a stack — some sort of sub-stack that renders as its own short stack in the ui, while graphite still knows its only mergeable once the downstack lands on main. eg: on a 27-pr stack, prs 1-16 are foundational work and 17-27 are a new scenario built on top. the top ones could be a brand new stack, but they obviously depend on the entire foundational work, so today the pr page renders the full 27-deep rail. i looked into multiple trunks (

gt trunk --add

), which gets me the visual split, but then merges land into the trunk branch instead of main and the cross-stack dependency awareness is gone... so it doesnt quite fit for in-flight stacks. is there anything like this today, or on the roadmap? (or a recommended way of dealing with huge stacks like this 😄 )

hey! there isn't a sub-stack view like that today and the multi-trunk limitation is right. Trunks merge independently, so the dependency link is lost (*https://graphite.com/docs/multiple-trunks*). The usual pattern for huge stacks is to land the foundational PRs first so the top half becomes its own short stack. I'll log this as a feature request with the team, no ETA to share today but I will get it to the team for review.