-
-
Notifications
You must be signed in to change notification settings - Fork 141
Description
Problem
My team have bought into Git Town as our stacked workflow tool of choice. We're loving the workflow so far and the productivity gains from not being blocked. It's also drastically reduced PR size as contributors no longer feel the need to submit work in large chunks out of fear of being blocked. Huge wins overall 🎉
However our one and only pain point is that we now have 30+ proposals open at any given time 😅. This makes it pretty hard to track which proposals belong to which stack. We like to review from the base up for any given stack, so this is a big point of friction for us during code review.
Our current method is to figure out what the base PR to any stack is (it'll be the one targeting the main branch), review it, take note of it's branch name, then find the PR that targets that branch. Rinse repeat until we're done. Refined Github makes this a little easier, but it's still not great:
Solution?
graphite.dev has a neat feature where it maintains a stack lineage for each proposal it creates in a stack.
This allows your team to easily visualise & navigate through your stack on Github.
It would be super helpful if Git Town could provide a similar feature, perhaps built into git-town sync and git-town propose?

