arxanas/git-branchless v0.3.10

on GitHub

To install or update git-branchless, run the following:

$ cargo install --locked git-branchless
$ git branchless init  # in your repository

NOTE: when installing this version with --locked, you may see a warning like this:

warning: package `crossbeam-channel v0.5.2` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked

This is safe to ignore. We are waiting for an upstream dependency to be updated to resolve this warning. This is tracked in #317.

Release highlights

This release introduces the following new commands:

• git sync (demo, docs): rebase all commit stacks on top of the main branch without checking them out.
• git reword (docs): update the commit message of one or multiple commits without checking them out (thanks to @claytonrcarter).
• git branchless bug-report: generate debugging information to attach to a Github issue.

Additionally, git undo has a breaking change; see below.

Changelog

Added

• EXPERIMENTAL: created git sync command, which moves all commit stacks onto the main branch (if possible).
• EXPERIMENTAL: created git reword command, which can rewrite commit messages anywhere in the commit tree.
• The --only-branches option can be passed to git smartlog to only show commits which are on branches.
• The git move command, and other commands which can move commits, now accepts the option --no-deduplicate-commits to skip commit deduplication.

Changed

• (#286) The smartlog now displays an icon next to the currently-checked-out branch.
• (#289) Changed output wording for git hide/git unhide.
• BREAKING: git undo now undoes the most recent operation by default (after confirming). The interactive behavior is available with the -i/--interactive flag.

Fixed

• (#267) Aliases like git amend are now installed only if the user does not already have aliases with the same name. Thanks to @rslabbert for implementing this.
• Improved performance up to 15x for git restack on large commit histories.
• (#280) Ambiguous commit hashes are no longer printed in output. (Additional characters of the hash will be appended as necessary.) Thanks to @yujong-lee for fixing this.

New contributors

Thanks to the following first-time contributors!

• @rslabbert made their first contribution in #267
• @claytonrcarter made their first contribution in #296
• @yujong-lee made their first contribution in #306

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.