Helpful Resources

• Updating stacks

Benefits

• No longer need to name branches
• Where I’m seeing benefits of removed friction
  • Removes the itch to make a “perfect PR” when it’s easier to iterate on old PRs
  • Frequently run in to bugs right after opening a PR, this iteration makes it easier to go back and fix it
    • gt co (wip stack) → gt modify → gt co (current tip) → cargo build/bolt up → continue working
  • Changes 1-line changes to site/docs/mareting were often pushed to main because it wasn’t worth the effort to make a PR. Now these are much faster to review.
  • Reduces common needs of cherrypicking
• Making changes it much more iterative and lower friction (”git branch” and “git commit” are now effectively the same thing)
• gt cli already has aliases for shorthands of everything
• Less push/pull friction, so changes are less diverged from main & origin
• Automatic rebasing of upstream stacks is super cool and super handy
• Linear-quality keybindings in web
• Encourages 1 stack to 1 Linear issue pattern
• Graphite Slack notifications are more helpful than GitHub’s
  • (Forest) Potential nit (not sure how big it is yet), it is quite noisy, and a bit hard to separate. This seems like the place to go if someone comments on a PR that you previously commented on. It might get better as I get used to it.
    • Image example
• AI summaries? Can’t tell how helpful this is.
  • This seems cool if it can generalize the overview, but it seems to just be a list of files changed
  • If it was good at writing instructions to test, that could be helpful
• There is a concept of “versions” of PRs, which quickly allows you to switch to the context in which a now “stale” comment was written. This is good for not getting overwhelmed by new commits when reviewing old review comments.
• gt checkout includes fuzzy searching branch names

Pain points for new users

• Docs are scattered and not very helpful for workflows
• Going back and “modifying” stacks feels weird and isn’t well discussed in the docs (see here)
  • (Andrew) If you accidentally create a new stack instead of modify, not very intuitive to delete the branch and pr (3 step process, github branch, github pr, and gt pop)