It should have just done a usual git commit

In the Git log, observe that the commit action actually sent git rebase -continue, which is not correct.

VS Code pops a dialog from Git, saying that the operation is not allowed.

Attempt to commit anyway through the Source Control pane.

Note that VS Code shows a warning that editing the commit is not allowed, even though Git specifically allows it here.Rename the commit description or make more local changes. Once the commit is soft reset, attempt to edit the commit.In the Source Control pane, use ‘Undo last commit’.It will prompt to amend the commit or add more. Git will start the rebase, and stop on the commit.In the editor for the interactive rebase, change a commit from pick to edit.In the terminal, do git rebase -i master.Create a new branch, and add at least one commit to the branch.

Now, instead of just allowing commits as usual, VS Code attempts to use git rebase -continue after altering a commit, which fails because there is still a commit pending that is not the original. This includes undoing them, changing the commit message, or adding more commits. git rebase -i allows the rebase to be stopped in in order to edit commits. As of a latest update, VS Code now does the wrong thing when using the Source Control pane during a git rebase command.

Visual studio code git editor