git_branchless/
lib.rs

1//! Branchless workflow for Git.
2//!
3//! # Why?
4//!
5//! Most Git workflows involve heavy use of branches to track commit work that is
6//! underway. However, branches require that you "name" every commit you're
7//! interested in tracking. If you spend a lot of time doing any of the following:
8//!
9//!   * Switching between work tasks.
10//!   * Separating minor cleanups/refactorings into their own commits, for ease of
11//!     reviewability.
12//!   * Performing speculative work which may not be ultimately committed.
13//!   * Working on top of work that you or a collaborator produced, which is not
14//!     yet checked in.
15//!   * Losing track of `git stash`es you made previously.
16//!
17//! Then the branchless workflow may be for you instead.
18
19#![warn(missing_docs)]
20#![warn(
21    clippy::all,
22    clippy::as_conversions,
23    clippy::clone_on_ref_ptr,
24    clippy::dbg_macro
25)]
26#![allow(clippy::too_many_arguments, clippy::blocks_in_if_conditions)]
27
28pub mod commands;