Skip to content

Commit f355014

Browse files
committed
Update Git tips article
1 parent 3f6e14e commit f355014

1 file changed

Lines changed: 13 additions & 1 deletion

File tree

_posts/2017-05-23-little-things-i-like-to-do-with-git.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
layout: post
33
title: "Little Things I Like to Do with Git"
44
date: 2017-05-23 14:39:29
5+
last_modified_at: 2025-06-02
56
categories: Web Development
67
meta: "Git is a bunch of fun"
78
---
@@ -224,7 +225,7 @@ that I’ve completed, I can just ask Git to pull up all of that information for
224225
me:
225226

226227
```bash
227-
$ git log --since=00:00:00 --all --no-merges --oneline --author=<your email address>
228+
$ git log --since='midnight' --all --no-merges --oneline --author=<your email address>
228229
```
229230

230231
This will `log` `--all` branches showing you the work that the specified
@@ -233,6 +234,17 @@ a simplified `--oneline` overview.
233234

234235
I have this aliased to `$ git today`.
235236

237+
### <ins datetime="2025-06-02">Yesterday’s Work</ins>
238+
239+
Similarly, if you want to remind yourself of yesterday’s work—in advance of your
240+
standup, for example—we have:
241+
242+
```bash
243+
$ git log --since='yesterday.midnight' --until='midnight' --all --no-merges --oneline --author=<your email address>
244+
```
245+
246+
This, predictably, is aliased to `$ git yesterday`.
247+
236248
## Generate a Changelog
237249

238250
Writing a CHANGELOG can be a little tedious; we have to look over all of the

0 commit comments

Comments
 (0)