gh-log

a.k.a. "wait, what did I do last week?"

This is an extension (plugin) for GitHub's gh CLI tool. It adds a gh log subcommand which is similar to git log but for actions you take on GitHub, such as creating or closing issues, reviewing or merging PRs, pushing branches and tags, etc.

gh extension install jake-low/gh-log

$ gh log --since '3 days ago'
Friday, March 21
work-org/monorepo
  12:03  created branch rewrite-in-rust
  12:04  pushed 1 commits to main (+71690 -58253)
         fe5c913 chore: full rust rewrite
  12:05  created PR "Rewrite the whole app in Rust!" (#60) from rewrite-in-rust (+71690 -58253)
  12:07  merged PR "Rewrite the whole app in Rust!" (#60) to main (+71690 -58253)
  13:18  commented on issue "Uhh was the Rust rewrite discussed anywhere?" (#61)
  13:27  closed PR "Revert 'Rewrite the whole app in Rust!'" (#62) (not planned)

Saturday, March 22
me/cool-side-project
  21:40  pushed 2 commits to main
         39cf6dc add fixme comment about RCE vulnerability (+4 -0)
         7bf6552 use more emojis in console output (+18 -18)
  21:43  created tag v0.119.0
  21:43  released v0.119.0
  
Sunday, March 23
nodejs/node
  17:10  opened issue "A proposal to combine null and undefined into one value" (#57601)
  17:19  commented on issue "A proposal to combine null and undefined into one value" (#57601)
  17:23  commented on issue "A proposal to combine null and undefined into one value" (#57601)
  17:28  commented on issue "A proposal to combine null and undefined into one value" (#57601)
  17:40  commented on issue "A proposal to combine null and undefined into one value" (#57601)
  
me/resume
  19:26  pushed 1 commit to main
         a08f063 add HTML to list of programming languages (+1 -0)

• --since <time>: show events since this time (default: 7 days ago). Accepts absolute or relative times, like 2026-11-03, yesterday, monday, or 3 hours ago. A date without a time means the start of that day.
• --until <time>: show events before this time. Accepts the same formats as --since; a date without a time includes that whole day, so --since monday --until wednesday covers 72 hours.
• --repo <owner/name>: only show events in this repository. May be repeated.
• --owner <name>: only show events in repositories owned by this user or organization. May be repeated, and combined with --repo.
• --commits: list the first few commits of each push.
• --all: show every event on its own line. By default, gh log collapses closely related events into a single line (for example, several comments on the same issue, or review comments followed by the review they belong to) and omits events that duplicate others (such as the push created by merging a PR). --all disables this behaviour to show every event separately.

GitHub's events API has some limitations that affect gh log.

• The events API does not immediately return the newest events. This means gh log will not immediately show your latest actions. The availability of recent events seems to vary but sometimes events take many hours before they appear in the API response.
• The events API only permits fetching of the first few pages of events. Trying to fetch older events than some cutoff will result in an HTTP 422 error. I'm not sure if the cutoff happens at a specific page number or event count, or if it is based on the age of the events requested. In any case, the effect is that gh log will not be able to display very old events, even if you pass a timestamp that is a long time ago for the --since option.

The gh-log program is offered under the ISC license. See the LICENSE file for details.