1

Can someone please explain to me the differences between these options for git rebase through visual studio code? Visual Studio Code Rebase Options

torek
  • 448,244
  • 59
  • 642
  • 775
Rob Newman
  • 11
  • 1

1 Answers1

1

Those aren't exactly rebase options. Compare to what happens when you type in a Google query:

how many weeks in a year
how many ounces in a gallon
how to screenshot on windows
Howie Mandel
Howl's Moving Castle

Your question is a bit like asking why these options popped up for howitzer in the middle of the question.

The screenshot you show—by the way, don't use screenshots if at all possible, but if you do, inline them (I did that for you here)—have brought up two basic Git commands:

  • git pull, which simply runs two commands for you—git fetch, followed by one of git merge or git rebase—and this gave you a way to invoke the use-rebase-as-the-second-command-style git pull; and
  • git rebase, which is the git rebase command (and needs more information).

The third option you got was to run a VSCode-specific thing that VSCode calls "git sync". This is not a Git command at all: instead, it's a sort of VSCode action that runs two Git commands for you, namely git pull followed by git push. The pull itself is a Git command, which then runs the two Git commands (fetch, plus whatever second one you've chosen by configuration, although in this case perhaps the selector overrides the configuration and makes the second command be git rebase anyway). See What does git sync do in VSCode for more about this.

torek
  • 448,244
  • 59
  • 642
  • 775