v0.4.0 #497
arxanas
announced in
Release notes
v0.4.0
#497
Replies: 1 comment 1 reply
-
Move with insert & exact is really useful, I've been using it quite a bit. Less need to |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
To install or update
git-branchless
, run the following:If you see an error like
failed to select a requirement libgit2-sys
, then you need to update your version of Rust. See the troubleshooting section.If you haven't already taken the user survey, please consider doing so!
Release highlights
🎉 This release includes the 1000th commit to git-branchless! 🎉
There are two exciting features in this release:
git move
accepts the-x
/--exact
and-I
/--insert
flags to move commits much more precisely than previously possible.git query
command as an interface to try out your revset queries.See Revset recipes for some ideas on how to use
git move
and revsets together or contribute your own.On a logistical note, we will be incrementing the minor version number by default in future versions of git-branchless. Minor versions will include new features and may include breaking changes (while we are still on version 0.x.y). The patch version number will be used for backward-compatible bug-fixes, as SemVer intended.
Changelog
Added
git branchless move
:--insert
flag #400) Added--insert
option to to insert the moved subtree or commits into the commit tree between the destination commit and its children, if any.git move
: Add--exact
option (closes #176) #450) Added--exact
option to move a specific set of commits elsewhere in the commit tree. They will be removed from their current location and any unmoved children (if any) will be moved to their closest unmoved ancestor. The moved commits will maintain their overall ancestry structure.git move
#447)--source
,--base
and--exact
options can all be provided multiple times to move multiple subtress, ranges and/or commits to the destination.--yes
option togit undo
to skip confirmation.git reword
to allow updating multiple, individual commit messages at once.git query
command to dump the results of revset queries.--delete-branches
option togit hide
.git branchless repair
command #435) Created thegit branchless repair
command, which is occasionally useful for cleaning up garbage-collected commits from the smartlog.git undo
.branchless.undo.createSnapshots
tofalse
.git record
command #391) created thegit record
command, which opens an interactive change selector for committing.Changed
cargo update
#422) Rust v1.61 or later is required to build.git smartlog
#472)git smartlog
no longer supports the--only-branches
option. Instead, usegit smartlog 'branches()'
.git move
will abort when trying to move public commits; you now have to pass--force
.git reword
, the marker line is omitted.Fixed
git restack -m
instead ofgit amend -m
#358) Adjusted the misleading suggestion that was printed when running agit amend
invocation which produced merge conflicts.git undo
#359) Fixed thesmartlog
output when runninggit undo
. Previously, it showed the smartlog as if you were still at theHEAD
location before thegit undo
.git var
first #387)git reword
now reads from$GIT_EDITOR
, etc. via thegit var
command.git smartlog
or similar, any commits which would show up are now kept live for garbage-collection purposes, even ifgit-branchless
didn't observe them being committed.This discussion was created from the release v0.4.0.
Beta Was this translation helpful? Give feedback.
All reactions