git-commands | Custom power-user git commands

git restore command is only available from git version 2.23+. I think you are using a git version below than that.

You can have the variables Build.QueuedBy and Build.QueuedById, it always will be the system identity, for example: [DefaultCollection]\Project Collection Service Accounts.

You can find here more info.

The operation is succeeded, this is not a "real" error, it's because git push is sending output to stderr, not stdout so PowerShell thinks it's an error.

How to prevent it?

There are several options but the shortest it's just to add --porcelain to the git push:

I expected vscode to offer a ready-made merged log. Instead, up to now, manual work seems needed.

The only automatically merged log of Source Control pane and Terminal view is in the vscode "Developer Tools" > "console", with the caveat that the terminal commands are not logged directly: you only see from a certain structure that there was a terminal command at that moment and then you can at least manually look up in your terminal history what it must have been - tricky, but not impossible if you desparately need to document or reconstruct the exact command sequence. Still you need the manual work here to assign the terminal commands to the right place in the Developer Tools console log.

There are other logs which do not include both, just either the Source Control pane or the Terminal view.

The easiest manually merged log is obviously the manual merger of the Git Output window (see In Visual Studio Code, how can I get a git log of all git commands executed in the Source Control pane?) manually put together with simple copies from the terminal commands+output.

There are other logs available which do not add any more value, for completeness: git reflog, git.txt, and history command in Terminal window.

Here is a detailed documentation which can probably be ignored because the manual merge of git log and terminal log should be the easiest way.

####

vscode Developer Tools console:

• run "C:\Users\USER\AppData\Local\Programs\Microsoft VS Code\Code.exe" --verbose or if it is in your Path just run code --verbose` from the command line.

• in Code select Help | Toggle Developer Tools and select the Console

• Find out which filters you need, e.g. a filename for a first test, or if you want to see only the Source Control pane commands, filter for "CommandService". You need to play around to find out, perhaps you just copy the whole log and filter it later.

Example: put a filter on "git -Watcher", search for "init" gives me:

TRACE telemetry/views.welcomeAction {viewId: "workbench.scm", uri:

"command:git.init?%5Btrue%5D"}

TRACE CommandService#executeCommand

git.init

vscode uses git.stage instead of git.add, which are synonyms, see Differencies between git add and git stage command

The search for a project file leads to the "DecorationsService" after the git.commit.

Terminal commands cannot be seen directly, but you see from the "typing information" in the terminal that there was an input in the terminal:

TRACE IPty#write [number] characters

followed by 4 "File Watcher" actions (tested with git status).

Though you cannot see the commands, you can reconstruct their sequence even when you have switched between Source Control pane and Terminal window.

Mind that this is just a session log in contrast to the saved git reflog. And it does not include any output.

####

git reflog:

For a global solution, there is the git reflog which has only commit/checkout/merge… log and does not show the exact command / output, but a summary, this is borrowed from History or log of commands executed in Git

####

git.txt:

vscode offers a git log, on Windows, this is C:\Users\USER\AppData\Roaming\Code\logs\[some hash]\git.txt

For more details and other locations, see Where are Visual Studio Code log files?

It starts like

telemetry/git.command {"properties":{"command":"git.init" …

####

Terminal history:

For the terminal history of commands, use history in the vscode terminal, this is borrowed again from History or log of commands executed in Git

This is just a session log in contrast to the saved git reflog.

One option would be to clone the repository afresh in a new folder, carry across the changes you require in the two files, and then commit and push the result.

Please try with below push script, which attached the PAT token in the git command to authorized the operation:

I contacted the CircleCI support. They are investigating this issue now, but they coudn't give me an ETA. I will edit my answer when the issue is fixed.

Edit: The issue was marked as solved today. 24. April 2019

It clones a git repository into your desired local path.

Use it whenever you need to work with a git repository in your computer.

Not install Git Credential Manager on your agent machine only cause the credentials won’t be stored, and you need to provide credentials for every time to connect with the remote repo in VSTS.

But there has the way to stop pop the SSO dialog (not authenticate by email address and password) by providing the PAT (authenticate by PAT), such as you can push change by the command: