innovationfere.blogg.se

Visual studio code git map
Visual studio code git map










visual studio code git map

Sure, I’ve added some extensions such as C#, mssql, Babel JavaScript, and transformer to address some gaps but by and large, I’ve found the experience to be more than sufficient for my needs. The “out-of-the-box”, “stock” experience with VS Code is truly fantastic and has provided me with just about all the functionality I’ve needed.

visual studio code git map

In fact, given the nature of my work recently I’ve found myself spending more time in VS Code than in VS 2017 over the past several months. The two screenshots show the same thing and are both correct.I’ve been using VS Code for quite some time now. There is also further development on master but it is above the screenshots and is not shown. It's still the same graph!ĭevelopment now continues just on dev: Await future(s), Minor refactor, and so forth. The two branches are displayed in the right-to-left order master–dev in the first screenshot and in the order dev–master in the second screenshot, but as I just remarked, that's meaningless. Thus we need to display three branches which are reduced to two, because the hotfix branch has now been merged into the other two and there will be no further development on it. The hotfix branch was then merged into master and also merged separately into dev. It's still the same graph showing the same chain of parentage vertically. In right-to-left terms, this line of parentage is horizontally displayed at the far right in the first screenshot and in the middle in the second screenshot - but that is irrelevant because right-to-left (horizontal) position of a branch has no meaning whatever. Then a hotfix branch was created and the "Fix app crash issue" commit was created on it, followed by Release 3146. I presume that you think of this as master. Here is what the drawing says - in both screen shots (reading from the bottom up):Īs we enter the picture from the bottom, a single chain of parentage represents both master and dev.

visual studio code git map

A little bending and stretching turns one into the other without any change in the node parentage indicated. The two drawings are, in other words, topologically identical.

visual studio code git map

They convey exactly the same node parentage information. If you look carefully you will see that on that basis your two screenshots are two perfectly valid ways of drawing the very same graph. Git history describes a directed acyclic graph of node parentage. Remember the old joke? Topologically, a donut and a coffee cup are the same object. Basically, you don’t know how to read a map. Is there anything I am missing while reading the graph on IntelliJ?












Visual studio code git map