![]() That way you don’t need to create a local branch if you aren't 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 icon and switch to an inline diff view.Ĭhecking out a commit can be beneficial in multiple ways. Then, right-click one of them and select Compare Commits. To compare any two commits in your branch, use the Ctrl key to select the two commits that you want to compare. You can use the list of branches at the top of the table to scroll between branches more easily and know immediately which branches appear in the graph. There's both line coloring and branch labels on the left side of the Local History view that help make it easier to trace which commits belong to each branch. You can then select any branch to add both the branch and its commits to a multi-branch graph view, which adds visual cues that make it more efficient to interact with multiple branches. New with version 17.7: When you open the Git Repo window, you start in the single branch view. You can also select your favorite diff configuration by selecting Diff Configuration (the gear icon). To display your commit in full screen, detach your Commit tab and maximize the Commit window by using the Maximize button. 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 through any local or remote branch without having to switch your branch. The Alt+ Up arrow 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 Resize.cs 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 (or by using the Ctrl+ 0, Ctrl+ R keyboard shortcut). 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |