Git rebase: Difference between revisions
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
<tt>git rebase</tt> reapplies commits on top of another base tip, removing the original commits. For more details on how rebasing works, and some concrete examples, see: {{Internal|Git Rebasing|Git Rebasing}} | <tt>git rebase</tt> reapplies commits on top of another base tip, removing the original commits. For more details on how rebasing works, and some concrete examples, see: {{Internal|Git Rebasing|Git Rebasing}} | ||
=Options= | |||
==--onto== | |||
git rebase --onto <''newbase''> | |||
Starting point at which to create the new commits. If the --onto option is not specified, the starting point is <font color=darkgray><''upstream''> (what does that mean?)</font>. It may be any valid commit, not just an existing branch name. | |||
==--fork-point== | |||
<font color=darkgray>TODO</font> | |||
Revision as of 00:51, 8 August 2019
Internal
Overview
git rebase reapplies commits on top of another base tip, removing the original commits. For more details on how rebasing works, and some concrete examples, see:
Options
--onto
git rebase --onto <newbase>
Starting point at which to create the new commits. If the --onto option is not specified, the starting point is <upstream> (what does that mean?). It may be any valid commit, not just an existing branch name.
--fork-point
TODO