Commands
>_
but absorb
Amends changes into the appropriate commits where they belong.
The semantic for finding "the appropriate commit" is as follows:
- If a change has a dependency to a particular commit, it will be amended into that particular commit
- If a change is assigned to a branch in the GitButler app, it will be amended into a commit there
- If there are no commits on that branch, a new commit is created there
- Changes are amended into the topmost commit of the leftmost (first) branch
Optionally an identifier to an Uncommitted File may be provided.
- If an Uncommitted File id is provided, absorb will be performed for just that file
- If no source is provided, absorb is performed for all uncommitted changes
If --dry-run is specified, no changes will be made; instead, the absorption plan
(what changes would be absorbed by which commits) will be shown.
Usage: but absorb [SOURCE] [OPTIONS]
Arguments
<SOURCE>— If the Source is an uncommitted change - the change will be absorbed. If not provided, everything that is uncommitted will be absorbed
Options
--dry-run— Show the absorption plan without making any changes--allow-merged— Allow targeting branches and commits that are already merged upstream.
By default, mutations refuse to touch history that has landed in the target branch, since the results tend to conflict on the next but pull.
Last updated on