Kevin Goslar

@sheldonhull http://github.com/Originate/git-town/releases/latest/download/git-town-windows-amd64.exe should give you the latest Windows binary

We will get this for free with goreleaser, see #1379

I like the idea, especially since there wouldn't be a performance impact. Right now synching a shipped branch re-pushes the branch to the remote. The new behavior would do the...

@arekkas did you have another Git client open, like IntelliJ of Github Desktop? They sometimes perform Git commands in the background. Git isn't thread-safe, it errs out when another Git...

Okay, allowing abort or continue sounds good as well. Good idea.

We have an end-to-end test for this scenario (except it doesn't use the Github API but this shouldn't matter here): https://github.com/git-town/git-town/blob/master/features/ship/supplied_branch/feature_branch/conflicts/feature_branch_merge_main_branch_conflict.feature. It shouldn't run `git merge --abort`. I guess this...

Yeah, implementing this using `--force-with-lease` sounds more secure. I like it!

Maybe use Git references like [git bug]( https://github.com/MichaelMure/git-bug/blob/master/doc/model.md) does.

If we go with the _orphaned git branch approach_, we would have to check out, read/modify, and delete that branch locally for each operation on it, since I consider that...

I did some experimentation by uncommenting the [logger for Git commands](https://github.com/MichaelMure/git-bug/blob/master/repository/git.go#L32) in `git bug`. Here is a set of commands that allows us to store/push/pull/read data (for example the Git...