There were large changes in git-trim
since last release.
Breaking changes
- Use a deduced base branch from remote
HEAD
s, rather than hard-coded default base branches. #127
The change will makegit-trim
to gracefully adapt to default branch renaming. It might break multi-base branching scheme such asgit-flow
as noted in the PR. git-flow users should setgit config trim.bases develop,master
.
Visible changes
Refactorings, internal changes, fixes, and cleanups
- Don't protect any branches by default #128
Previous default value was just a fail-safe. - Don't use push upstream to classify branch #136
I've (mis)used push upstream from the first release with misunderstanding. I've added a survey - Separate core and lib #120
- Use typed branch #121
- Introduce merge tracker #122
- Simplify trim plan data structure #125
- Many fixes and cleanups: https://github.com/foriequal0/git-trim/pulls?page=1&q=merged%3A2020-06-14..2020-08-03