Kevin Goslar

Interesting edge case, thanks for reporting it. Technically your `example` branch shouldn't have a tracking branch since the remote rejected the push. Git Town saying that the branch is not...

Closing this as out of scope for Git Town.

Writing down a (dopey) idea for how to possible support this (widespread) use case. This would only work if you amend commits and never change the commit messages: 1. You...

I agree it would be much better if Git Town would support the full range of changing commits, including changing content, commit messages, or reorganizing commits via interactive rebase. Another...

When the user runs `git fetch` and there were changes to the remote branch: we no longer detect them and `git push --force` will overwrite them. Bad situation. When the...

An alternative would be storing the SHA of the remote branch in the runstate file as well. When the user runs `git fetch` and there were changes to the remote...

@ruudk Git Town 13.0 introduces support for your scenario. I'm going to close this ticket as completed. If there are additional ideas of feedback, please don't hesitate to comment on...

Charlie!! 🎉 Please note the updated terminology for "prune" that this ticket proposes. The old `prune-branches` command deleted branches whose tracking branch is gone, i.e. branches that were shipped or...

Thanks for the helpful feedback 🙏 > I often use prune-branches more as a cleanup than anything and don't want to deal with syncing other branches at the time. Can...

Thanks for the detailed feedback! Your use cases are pretty representative for how staff-level engineers work. Git Town should support such use cases fully without requiring workarounds. I have brainstormed...