Kevin Goslar

steps to reproduce: - have branches A, B, C - branch A is current, branch B is the previous branch - delete branch A on the remote - run git...

- [ ] `git town set-parent` changes the proposal - `git kill` - [ ] closes the proposal for the current branch - [ ] updates the proposals of child...

new config option: "git-town.sync-before-ship"

2

### Motivation In the typical usage scenario, it often doesn't make sense to sync right before shipping. - I sync my branches regularly using `git sync` or `git sync --all`...

we don't use it anymore

git ship: prepopulate the commit message with the PR title and body

2

- this is about the commit message that the user edits when running `git ship` - right now it uses a rather simple default Git commit message: ` (#)` -...

At the end of running `git sync --all` it always performs a `git push --tags`, even if there have been no updates at all.

steps to reproduce: ```bash # create a local branch git hack foo # rename the branch to something else git rename-branch bar ``` expected outcome: the branch gets renamed actual...

- walk through the dev environment - code base checked out - VSCode with Go plugin - run the tests - walk through the codebase - website - end-to-end tests...

better auto-completion

1

The static auto-completion provided out of the box by Cobra isn't enough for Git Town since some commands also need to auto-complete Git branch names. - [ ] try `ValidArgsFunction`...

option to not push new commits on the main branch

2

Extracted from https://github.com/git-town/git-town/issues/2223#issuecomment-1518338374: When the `protected-main-branch` option is set, https://github.com/git-town/git-town/blob/5ef3afa47c2c0d6a898bcd525ad11f4d69b3136d/features/sync/current_branch/feature_branch/rebase_sync_strategy/sync_current_feature_branch_using_rebase.feature#L20 should not happen. Instead, if it finds an unpushed commit on `main`, it should print an error notifying the user...