You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2024. It is now read-only.
Git rebase has an option called --rebase-merges. This keeps any merge commits that are on the branch to be rebased. Imagine a scenario where a branch is a combination of several other branches, but the authors want to rebase it onto master. In the current situation all the merge commits are lost and a single, linear branch will be created. --rebase-merges allows to keep the original history of that branch, along with all the merge commits, and just rebases it onto the target branch.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Git rebase has an option called
--rebase-merges
. This keeps any merge commits that are on the branch to be rebased. Imagine a scenario where a branch is a combination of several other branches, but the authors want to rebase it onto master. In the current situation all the merge commits are lost and a single, linear branch will be created.--rebase-merges
allows to keep the original history of that branch, along with all the merge commits, and just rebases it onto the target branch.The text was updated successfully, but these errors were encountered: