![]() ![]() I tried having only changes locally versus pushing up to GitHub, but that doesn’t add the dash back. At first when I started writing this blog post, I figured SlnExp was using the exact same icons and tooltips, but clearly something is different in a Git repo. So although we’re supposed to interpret this as “unchanged”, it’s interesting that the tooltip doesn’t have the dash between Checked and In. Sure, it’s a little strange at first (as mentioned above), but then you adjust and go on with your life.įor example, this is a Git repo with `git status` that has nothing to commit and working tree clean. View commit information in a treeview (snapshot of all changes) Open the file to view the history, and then Press F1 and select/type 'Git: View History', 'Git: View File History' or 'Git: View Line History'. View the history of a line in a file (Git Blame). ![]() My guess (and this is just my guess, considering I haven’t been on the team in ages) is that they went with the existing set of check-in and check-out icons, hence mapping their semantic meaning to the Git states. View and search git log along with the graph and details. ![]() ![]() But Visual Studio users are used to icons have certain meaning. So “check in” and “check out” states don’t directly map. Let’s pause for a second and consider the workflow of Git being DVCS. Where you can now Right Click to “check out” your file or just simply start editing to “check out” your file. When you first create a project, you’ll notice that the files have a green + icon, indicating that this file is newly added, but not checked into source control.Īnd after you’ve check-in your new files, Tl dr – when using Git, the blue pad lock icon means “file is unchanged,” but why didn’t they update the tooltip? In TFVC, SlnExp uses “Checked-in” but in Git, SlnExp uses “Checked in” (no dash), so why not change the words?įor non-windows readers who are interested in what TFVC (a centralized VCS) looks like or those who want more context, here’s a brief overview of what a Solution looks like under Team Foundation Version Control (aka TFS, aka VSO, aka VSTS, etc.) Using Team Foundation Version Control in Solution Explorer Now I have created a very simple playbook using the Visual Code Editor. Press Ctrl+s to save it with a different name, I will save it as ' playbookvsc.yaml '. Click on File New File which will create a new file. At first I thought, “wait a sec… I just created this repo and solution, why are these files locked?” Anyone who has used Visual Studio for a while knows what I’m referring to. Now we can create a new file and start by creating a new playbook using the visual editor. This blue pad lock icon got me the first time I opened a Git-based solution. ![]()
0 Comments
Leave a Reply. |