The “Tray” const was added to the list, giving it a type of Electron.Tray, so I could put the app in the Taskbar tray (or Mac tray thingy at top of screen). Now it is time to figure out the what – what was changed in the line…īy clicking on the Compare with Previous… command in the context menu for the main.js file listed in the Changes list for that commit, you’ll see the file diff view appear.Īnd now we have “the what” for what has changed in the file. Seeing the Commit Details appear in Team Explorer answers the part one of my scenario – the when. But line 3, the one I’m interested in, was last modified in commit fd80ad89.Īs any long time Visual Studio user will do… let’s click the fd80ad89 and see what happens! In the above example, lines 1-2 were last modified by commit ID 44af5057 (most likely my initial commit). This window shows for each line what was the last commit that modified it.
The Blame / Annotate window will appear on the left hand side. anywhere in the file, right-click and select Source Control – Blame (Annotate) open the file that contains the line in question (either via Double-Click in Solution Explorer or File – Open – File provided you are connected to the repo in Team Explorer)Ģ.
#GIT ANNOTATE CODE#
#GIT ANNOTATE SOFTWARE#
When in Rome… but I often muse what would be the equivalent of commercial airline pilots who have to reskill like we do in the software industry. I was happy to see this command referred to as Annotate in Visual Studio 2015, but a bit saddened to see now called Blame (Annotate) in Visual Studio 2017. Why would I ever want to put myself into a position of having people call me out publicly via my code and blame me? But as I said in my previous post, Blame doesn’t mean “to imply blame” but rather “look up the commit that changed this line of code.” I share this story because the first time I saw “Blame” on GitHub, I felt the same emotion as I did as a little kid. Unfortunately, the teacher completely misread why I was crying (she thought I was acting out for attention) and scolded me, etc., which was my first foray into the self-fulfilling prophecy*. I thought perhaps I’d get into serious trouble when I got home or lose my recess or something.
I didn’t know what was going to happen to me for getting it wrong. When the teacher said no that was wrong, I broke down sobbing from fear and embarrassment. I thought it was ‘D’ but the answer was ‘C’. I remember once in first grade (6 years old) being asked by the teacher for the answer to a multiple choice question. I told think anyone ever realized how scared I was of the world (if not plain neurotic) as a small child. Today we’re going to rinse and repeat this scenario within Visual Studio.
#GIT ANNOTATE HOW TO#
Previously, I mentioned how to use Blame on to find the commit that changed a specific line.
0 kommentar(er)
