Releases: foriequal0/git-trim
Release v0.4.3
Updated dependencies.
Release v0.4.2
Enhancements
- Print why a branch is skipped #170
https://github.com/foriequal0/git-trim/pulls?q=merged%3A2020-10-15..2020-10-20+sort%3Aupdated-desc+
https://crates.io/crates/git-trim/0.4.2
Release v0.4.1
Enhancements
- Fallback base branches to
refs/remotes/*/HEAD
#168 - Print detailed error when no base is found # 169
- Upgrade rust-toolchain to 1.47.0 #167
https://github.com/foriequal0/git-trim/pulls?q=merged%3A2020-10-14..2020-10-14+sort%3Aupdated-desc+
https://crates.io/crates/git-trim/0.4.1
Release v0.4.0
Here's the list of (subjectively) important changes from v0.3.2.
Enhancements
- Use a deduced base branch from remote
HEAD
s, rather than hard-coded default base branches. #127 #145
The change will makegit-trim
to gracefully adapt to default branch renaming. It might break multi-base branching scheme such as git-flow as noted in the PR.git-flow
users should setgit config trim.bases develop,master
. - Preserve worktree branches #130
- Associate local and upstream/remote branches to prevent dangling states #140, #144
- Classify non-tracking local branches and non-upstream remote-tracking branches too #147, #163
- Print shorthand name instead of verbose refname #106 #108
- Print detailed messages why branches are filtered #162
Breaking changes
Release v0.4.0-alpha.4
This is a release note after v0.4.0-alpha.2 release.
Please refer previous release note https://github.com/foriequal0/git-trim/releases/tag/v0.4.0-alpha.2
I've missed some commits in alpha.3, so I skip it.
Breaking changes
- Merge
--scan
into--delete
#163
It also removed--delete all
option, local non-tracking branches scanning by default. - Don't protect local branches that just track bases's upstreams #164
Enhancements
- Print detailed messages why branches are filtered #162
https://github.com/foriequal0/git-trim/pulls?q=merged%3A2020-08-22..2020-09-08+sort%3Aupdated-desc+
Release v0.4.0-alpha.2
This is a release note after v0.4.0-alpha.1 release.
Please refer previous release note https://github.com/foriequal0/git-trim/releases/tag/v0.4.0-alpha.1
Breaking changes
- Require a scope for ranges #153
- Many changes in
--delete
options.
Enhancements
- Associate local and upstream/remote branches to prevent dangling states #140, #144
- Classify non-tracking local branches and non-upstream remote-tracking branches too #147
- Notify when the remote HEAD is changed #145
Fixes and refactorings
- Fix crash when branch does not have common ancestor #149
- Classifier has been rewritten #157
- https://github.com/foriequal0/git-trim/pulls?q=merged%3A2020-08-04..2020-08-21
Release v0.4.0-alpha.1
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
Release v0.3.2
Release v0.3.1
Release v0.3.0
Breaking changes
There are subtle differences between stray branches and gone branches. Also, CLI options are renamed. However, deleting gone branches is an unsafe operation. I didn't expect users to use it by default.
- Refine and change to stray branches from gone branches #77
- Fix misclassification when local is the only stray branch #79