Kevin Goslar

I think the default should be that developers ship their own branches. The reason is DevOps: developers should be responsible for the code they write through the entire lifecycle of...

Hi @cirego, thanks for the experience report! This happens to me all the time as well! 😆 You describe clientside branch protection. I think all branch protection should happen on...

I agree that the use case you describe is surprising and unwanted behavior. But it would be even more surprising and unwanted if somebody makes the effort to configure Git...

:+1: I like both ideas

Good thing that our specs are in Ruby. `Process.kill("INT", pid)` seems to be the ticket here. If this is hard to test, I think its fine without tests though. The...

Catching signals in Go: ```go signals := make(chan os.Signal, 1) signal.Notify(signals, os.Interrupt) server := NewServer() server.Run() select { case

Since this is for "delivering" larger bodies of work onto specific branches/environments, we could name this command `git deliver`. One would use it with the target branch name: `git deliver...

Thanks for this bug report @cirego! As a friendly reminder reading your backstory, there are also the `git town append` and `git town prepend` commands, which create a new branch...

We have [tests for this case](https://github.com/Originate/git-town/blob/master/features/git-town-sync/folder_does_not_exist_on_main_branch/no_conflict.feature) already. How do they pass when this is still an issue?

Thanks for the detailed bug report, John! Interesting edge case. You are right that if `git push -u origin style-update` fails, then running `git town continue` should run this command...