From the course: Coding Exercises: Git
Unlock the full course today
Join today to access over 24,800 courses taught by industry experts.
Identifying your changes - Git Tutorial
From the course: Coding Exercises: Git
Identifying your changes
(upbeat music) - [Instructor] In a multi-user environment with a large history, it's harder to detect when the changes were made by an individual. So how would you look for specific changes that only you made to a specific line of text? I'll give you a couple of seconds to think about how you do something like this. (upbeat music) All right, that's just perfect for the git blame command. It's sort of the cousin of the git log command, but it works on individual files and gives you more information about who changed what on a specific file. Let's check out our index.HTML file that's in this build folder, and it's right here, to see what sort of changes have been made to the file by individuals. So I can just do a git blame and then look for the build folder and look for this index.HTML file. Now, if you keep scrolling through this, it's going to show you every single change that was done and it's also going to show…
Contents
-
-
-
Cloning with limited history1m 33s
-
(Locked)
Adding to a previous commit4m 36s
-
(Locked)
Identifying your changes2m 26s
-
(Locked)
Managing multiple remotes2m 42s
-
(Locked)
Cleaner logs3m 25s
-
(Locked)
Using Git to hunt down bugs5m 7s
-
(Locked)
Working on multiple branches3m 19s
-
(Locked)
Creating a .zip file2m 57s
-
(Locked)
Getting rid of quick fixes4m 48s
-
(Locked)
Marking items without branching4m 8s
-
(Locked)
Removing untracked files2m 44s
-
(Locked)
Renaming branches2m 31s
-
(Locked)
Remove local, keep master3m 15s
-
(Locked)
Picking specific commits4m 30s
-
(Locked)
Creating a safety net for fixes2m 51s
-