In this case, you can just checkout the tip of the remote branch that you would like to review. That way you don’t need to create a local branch if you are not planning on contributing to it. It can also be helpful if you would like to review code from a remote branch (a colleague’s branch, for example). For example, it allows you to go back to a previous point in your repository’s history where you can run or test your code. If you prefer an inline diff, you can use the diff configuration options gear and switch to an inline diff view.Ĭhecking out a commit can be beneficial in multiple ways. When you find a commit that you want to focus on, select the Open in New Tab button to open the commit on a different tab. You can browse though any local or remote branch without having to switch your branch. The Alt+Up arrow key or Alt+Down arrow keyboard shortcuts allow you to jump between these sections.
For example, the previous screenshot shows the changes that one commit introduced to the Files.csproj file.
You can check the changes that a commit has introduced by selecting them, which shows a difference. Local History shows the rest of commits tracked by your local repository.Ĭommit: Selecting any commit in the Graph section opens its details.Outgoing shows your local commits that you still haven't pushed.Incoming shows incoming commits that your team has been contributing.Graph: This section visualizes the state of your branch. If you're working on multiple features at the same time or if you want to explore ideas without affecting your working code, branching can be helpful. The Git Repository window contains three main sections, as numbered in the preceding screenshot:īranches: Git empowers users to multitask and experiment with their code through branches. You can also access the Git Repository window by selecting the outgoing/incoming links in the Git Changes window and on the status bar.
To get started, open the Git Repository window by selecting Git Repository on the View menu. You can work remotely with the Git provider of your choice, such as GitHub or Azure DevOps. For example, you might need to get a good picture of what your team has been working on or maybe compare two commits to investigate a bug. But there are times when it makes more sense to focus on your Git repository. The Git Changes window provides a seamless way to interact with Git while coding without having to switch away from your code. Applies to: Visual Studio Visual Studio for Mac Visual Studio Code
0 kommentar(er)
