Kevin Goslar

https://github.com/git-town/git-town/issues/2224 tracks the implementation of this idea. I'm closing this ticket as a duplicate. Please add additional comments in the linked issue.

Merging this ticket into #2715

Challenges of the proposed human-readable config file ("git-town.yml") are: 1. It's another tool-specific config file, for a non-essential tool that might not be used by everybody on the team. Some...

Information about branch ancestry could be stored in the form of PRs on the code hosting service. See https://github.com/git-town/git-town/issues/1297. This works best with a workflow where all feature branches immediately...

Argument for a centralized config server: https://github.com/git-town/git-town/issues/2711

Decision has been made to replace the Git-based configuration system with a [config file](https://github.com/git-town/git-town/issues/2748) for the long-lived configuration options. Lineage gets [synchronized via proposals](https://github.com/git-town/git-town/issues/2745) and in the future via a...

Here is what I think happened: - You run `git sync` on the `argon2-value-cli` branch. - The files `go.mod` and `go.sum` on that branch conflict with updates on `master`. -...

Great to hear that Git Town is useful to your team! I agree that Git Town is in a good position to become a first-class tool for stacked development. To...

This is pretty brilliant, thanks for sharing! I especially like the idea to add the stack into the original PR description. This is MUCH better than describing the stack in...

We can certainly host this under the `git-town` organization on GitHub! It would have to be its own repo because that's how the GitHub marketplace works. Do you have bandwidth...