
Select providers" to see available SCM providers. Start typing and you will see suggestions for extension categories like debuggers and linters. If you would like to install another SCM provider, you can search on the scm providers extension category in the Extensions view ( ⇧⌘X (Windows, Linux Ctrl+Shift+X)). The Source Control Providers view shows the detected providers and repositories, and you can scope the display of your changes by selecting a specific provider. To turn on the Source Control Providers view, select the overflow menu in the Source Control view ( ⌃⇧G (Windows, Linux Ctrl+Shift+G)), hover over Views, and make sure that Source Control Repositories is marked with a check. For example, you can open multiple Git repositories alongside your Azure DevOps Server local workspace and seamlessly work across your projects. VS Code has support for handling multiple Source Control providers simultaneously. Tip: Click on an extension tile to read the description and reviews in the Marketplace.

Reset git reset //re-sets the current pointer to the given commit.

git checkout branch //means switching branches. If no path is given, git moves HEAD to the given commit (thereby changing the commit you're sitting and working on). git checkout // restores path from your last commit. If no branch is given, git assumes the HEAD commit. Tells git to replace the current state of paths with their state in the given commit. Now that you know the hash of the commit you want to go to you can use one of the following 2 commands: git checkout HASH Which will give you a compact list of all the commits and the short version of the SHA-1 hash. To do that all you need it the SHA-1 hash of the commit which you can easily find checking the log with the command: git log -abbrev-commit -pretty=oneline Sometimes when working on a git repository you want to go back to a specific commit (revision) to have a snapshot of your project at a specific time. Go to a particular commit of a git repository

Now, focus on this line of the gobbledegook: git branch If this option is omitted, the current HEAD will be used instead. It may be given as a branch name, aĬommit-id, or a tag.

The new branch head will point to this commit. Search through the subsequent text for the word "commit". Git-branch - List, create, or delete branches A great related question is: How the heck do you figure this out using the -help option of git? Let's try this: git branch -help
