Skip to content

Commit

Permalink
remove docs for --continue since not really needed anymore
Browse files Browse the repository at this point in the history
Signed-off-by: Kipras Melnikovas <[email protected]>
  • Loading branch information
kiprasmel committed May 28, 2022
1 parent a919e3c commit ee87bd0
Showing 1 changed file with 0 additions and 10 deletions.
10 changes: 0 additions & 10 deletions git-stacked-rebase.ts
Original file line number Diff line number Diff line change
Expand Up @@ -1427,16 +1427,6 @@ git-stacked-rebase <branch> [-a|--apply]
2. but wil not push the partial branches to a remote until --push --force is used.
git-stacked-rebase [<branch>] (-c|--continue)
(!) should be used instead of git-rebase's --continue
...because, additionally to invoking git rebase --continue,
this option automatically (prompts you to) --apply (if the rebase
has finished), thus ensuring that the partial branches
do not go out of sync with the newly rewritten history.
git-stacked-rebase <branch> [--push|-p --force|-f]
1. will checkout each branch and will push --force,
Expand Down

0 comments on commit ee87bd0

Please sign in to comment.