Feature request: show an overview of the stack with sync info

[cannonpalms]

I would love to have a command that shows me an overview of the stack with information about how synced or out-of-sync the stack is. The most crude version of this would be the output of git-town branch + a simple asterisk/indicator on branches that are out of sync. Taking it one step further, we might devise a way to show something akin to N commits ahead, M commits behind from git status. Two signals seem valuable:

1. Is my stack synced with the remote base?
2. How out of sync (+/- commits, etc.) is my stack with the remote base?
3. Is my stack synced with itself (internally in-sync)
4. How out of sync (+/- commits, etc.) is my stack with itself?

I don't think this feature exists yet, and I did a cursory search of open issues and didn't find anything similar (but I very easily could have missed both!).

---

Example

Perhaps something like this would be a cool start? You could add other useful info I am sure, (maybe head/tail commit SHAs).

main
  ╰─ feature1a (0 commits ahead, 2 behind)
    ╰─ feature1b (5 commits ahead, 1 behind)
*     ╰─ feature1c (1 commit ahead, 3 behind)
  ╰─ feature2a (0 commits ahead, 2 behind)

[kevgo]

Great idea! This would be behind a CLI flag and/or config option.

[cannonpalms]

Great idea! This would be behind a CLI flag and/or config option.

I take it that you're referring to a flag on branch?

---

Any feedback on what information might be useful to display? Do you similarly find yourself wanting a quick overview of the state of a stack? (unsure how frequent your use is)

[kevgo]

Yeah, I think a CLI flag like git town branch --status to show just the ahead/behind information could be useful.

Another option would be something like git town branch -vv, mirroring what git branch -vv provides. That would feel pretty natural to Git users and avoids inventing a new mental model.

Personally, I probably wouldn't use it that often since I tend to just run git sync --all when I'm unsure whether things are in sync. But I did hit a case last week where I couldn't sync a stack, and having quick visibility into the ahead/behind state would have been helpful.