Before submitting
Area
apps/server
Problem or use case
Managing threads over branches is bit brittle (currently on v0.0.21) specially when branches depend on other branches. I typically split a unit of large work over multiple prs (a stack) in order to make it easy to review by myself and coworkers.
Proposed solution
git-spice makes managing a stack easier to manage. It would be great if t3code natively supported git-spice.
Why this matters
A stack of PR is always better than very large prs and managing a stack can be intense with no tooling.
Smallest useful scope
create a branch with gs branch create -m 'description of the branch then use gs stack submit so submit the stack. This would already be quite helpful as I can deal myself with restack, splitting etc..
Alternatives considered
- Graphite. Proprietary software and needs graphite account.
- Status quo. Leaves me to manually deal with the stack, rebasing, force pushing. git-spice makes this easy.
Risks or tradeoffs
No response
Examples or references
No response
Contribution
Before submitting
Area
apps/server
Problem or use case
Managing threads over branches is bit brittle (currently on v0.0.21) specially when branches depend on other branches. I typically split a unit of large work over multiple prs (a stack) in order to make it easy to review by myself and coworkers.
Proposed solution
git-spice makes managing a stack easier to manage. It would be great if t3code natively supported git-spice.
Why this matters
A stack of PR is always better than very large prs and managing a stack can be intense with no tooling.
Smallest useful scope
create a branch with
gs branch create -m 'description of the branchthen usegs stack submitso submit the stack. This would already be quite helpful as I can deal myself with restack, splitting etc..Alternatives considered
Risks or tradeoffs
No response
Examples or references
No response
Contribution