1
0
Fork 0
mirror of https://github.com/tldr-pages/tldr.git synced 2025-07-31 00:55:29 +02:00
tldr/pages/common/git-rebase.md
Managor db25f60eb1
git-*: convert options to longform and minor fixes (#13441)
Co-authored-by: spageektti <git@spageektti.cc>
Co-authored-by: Fazle Arefin <fazlearefin@users.noreply.github.com>
2024-08-31 13:06:48 +02:00

37 lines
1.3 KiB
Markdown

# git rebase
> Reapply commits from one branch on top of another branch.
> Commonly used to "move" an entire branch to another base, creating copies of the commits in the new location.
> More information: <https://git-scm.com/docs/git-rebase>.
- Rebase the current branch on top of another specified branch:
`git rebase {{new_base_branch}}`
- Start an interactive rebase, which allows the commits to be reordered, omitted, combined or modified:
`git rebase {{--interactive|-i}} {{target_base_branch_or_commit_hash}}`
- Continue a rebase that was interrupted by a merge failure, after editing conflicting files:
`git rebase --continue`
- Continue a rebase that was paused due to merge conflicts, by skipping the conflicted commit:
`git rebase --skip`
- Abort a rebase in progress (e.g. if it is interrupted by a merge conflict):
`git rebase --abort`
- Move part of the current branch onto a new base, providing the old base to start from:
`git rebase --onto {{new_base}} {{old_base}}`
- Reapply the last 5 commits in-place, stopping to allow them to be reordered, omitted, combined or modified:
`git rebase {{--interactive|-i}} {{HEAD~5}}`
- Auto-resolve any conflicts by favoring the working branch version (`theirs` keyword has reversed meaning in this case):
`git rebase {{--strategy-option|-X}} theirs {{branch_name}}`