Crate branchless
source · [−]Expand description
Branchless workflow for Git.
Why?
Most Git workflows involve heavy use of branches to track commit work that is underway. However, branches require that you “name” every commit you’re interested in tracking. If you spend a lot of time doing any of the following:
- Switching between work tasks.
- Separating minor cleanups/refactorings into their own commits, for ease of reviewability.
- Performing speculative work which may not be ultimately committed.
- Working on top of work that you or a collaborator produced, which is not yet checked in.
- Losing track of
git stashes you made previously.
Then the branchless workflow may be for you instead.
Modules
Sub-commands of git-branchless.
Core algorithms and data structures.
Tools for interfacing with the Git repository.
The command-line options for git-branchless.
Testing utilities.
Utilities to control output and render to the terminal.
Utility functions.
Macros
Create a set of views with unique names.