From the course: Coding Exercises: Git
Unlock the full course today
Join today to access over 24,700 courses taught by industry experts.
Cleaner logs - Git Tutorial
From the course: Coding Exercises: Git
Cleaner logs
(videogame chiming) (bell dinging) (videogame chiming) - [Instructor] Git logs are a great way to take a peek at your history, but sometimes the history is too long, and you don't want to go through all of it. How can you get a more concise commit history within a date range containing a specific keyword? I'll give you a couple of seconds to think about how you would do something like this. (vidiogame whirling) (8-bit music) (vidiogame whirling) Most of us take the git log command for granted. It gives us a list of all of the commits along with the messages, the dates and these longer hashtags that we can use to refer to them. Let me go ahead and hit the Q key to get back. There's a lot of power in the git log statement that you can use by accessing different flags. So the first, and my favorite, is the oneline flag. So if I say git log oneline here, and I'm always mistyping this by forgetting that E, just saying…
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
-