v0.5.0
To install or update git-branchless
, run the following:
$ cargo install --locked git-branchless
$ git branchless init # in your repository
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 is primarily a bugfix release for revset-related issues. Thanks to @claytonrcarter and @pokey who fixed several bugs!
git reword
gained the--fixup
flag, and can now reword merge commits.- An experimental
git submit
command was added (discuss).
Changelog
Added
- (#508) Added
exactly(<revset>, n)
revset function to allow assertions on the number of commits within a set. - (#509) Users can now define custom revset aliases.
- (#533)
git reword
can now reword merge commits. - (#534)
git record
now accepts a--detach
option to avoid moving the current branch. - (#538)
git reword
now accepts a--fixup
option to convert regular commits intofixup!
commits (for use withgit rebase --autosquash
) - (#541) EXPERIMENTAL: Created
git submit
command. Discuss at #564.
Changed
- (#543) Commands will produce a better error message for certain unsupported sparse checkout configurations.
Fixed
- (#507) The
messages()
revset function now ignores trailing newlines in commit messages. - (#512) Fixed so that the setting for
--color
is now respected. - (#512) Fixed so that you can pass
--color
anywhere in the command-line, not just before the subcommand. - (#513) Fixed some false positives for hints to run
git restack
when printing the smartlog. - (#518) Fixed the suggested flag in the error message when attempting to rewrite public commits.
- (#539) Fixed parse errors for certain single-quoted string literals in revset expressions.
- (#559) Fixed precedence for parentheses in revset expressions.
- (#569) Fixed the reversed output order of the results of
git query
.
New contributors
Thanks to the following first-time contributors!
If you're interested in contributing, check out the Developer Guide in the Wiki, or post in the Discussions or Discord server to ask any questions.