When working in git, you most commonly trace a repository’s history using commits’ SHA-1 hashes. To revert to a previous commit, you might write something like this: $ git revert 883c3dc85a49d98da649 The problem is, we tend not to think in hashes. Rather, we wonder what changes we made yesterday, or remember that a now-broken piece of code worked perfectly a week ago. Although we can use git log t
![Working with dates in Git](https://cdn-ak-scissors.b.st-hatena.com/image/square/1eee54ca8f5ca99a8ec0fca3f985da9e94a0dadc/height=288;version=1;width=512/https%3A%2F%2Falexpeattie.com%2Fassets%2Fimages%2Fmeta%2Fdefault-og.png)