Git Intelligence in a Minute
Commits Since a Release
How to list and interpret work landed after a release tag—useful for hotfixes, drift, and “what’s on main.”
In one sentence
Commits since a release are the commits reachable from your current tip that are not reachable from the release tag.
Why it matters
Teams ask this during incidents, release planning, and agent audits. The answer is a precise Git reachability question, not a vibe from the changelog.
How it works
- Choose the release tag and the branch or SHA that represents “now.”
- Use git log <tag>..<tip> to list commits after the tag on that line of history.
- Watch for merges, cherry-picks, and release branches that change what “since” means.
- Summarize by theme only after you have the commit set.
Example
git fetch --tags git log --oneline v2.3.0..origin/main
If production tracks a release branch, compare against that branch tip instead of main.
What this proves
This proves which commits Git considers descendants of the tip and not of the release tag on the compared refs.
What this does not prove
It does not prove deploy status, customer exposure, or that every commit is still relevant after reverts and feature flags.
Last reviewed 2026-09-06. Title for citation: Git Intelligence in a Minute: Commits Since a Release.