Hey! Not really a "how do I" but I find the workflow for collaboration on a stack really unclear. When you should run

gt get

, when you should run

gt sync

, etc. So far my understanding is something like: when you start collaborating with other people on a branch you should run

gt get

on this branch just once. Afterwards you can get their changes with

gt sync

. Is that correct? In general I wish the docs would include a full example of a workflow with two people collaborating on a stack, occasionally on the same pull request, and occasionally on different pull requests.

Great suggestion - Cc @Pranathi Peri & @Stephen Pinkerton for viz

Hey Noe, we actually have a Graphite cheatsheet in the works that we'd love to share with you soon that will hopefully help answer these questions!

Hey Noe!! I just revamped our introduction to Graphite doc to be a little more visual/clear - I'm planning on creating one very similar around collaboration like you've suggested in the coming days!

Hello! Thanks for your work 🙂 Any news on the docs around collaboration?

Posting here mostly to get the update when the new cheat sheet is out, but wondering if there are any tips or gotchas on collaboration that you can recommend until then. I've mostly been using stacks solo, but recently was doing something collaboratively with a colleague and ran into some unexpected issues. From our experience it seemed that if you weren't tracking all the branches that are part of a stack (both your own and your collaborator) and you submitted a stack it would un-parent anything you weren't tracking, is that correct? I also didn't see anything that looked like a version of

gt get

that would get and sync all branches that are in the stack, including ones that you weren't tracking meaning I need to do this manually for anything my collaborators layer on top of my stack (and vice-versa)