git tpl log¶
Read the template's source commits, formatted as a compact changelog.
Without a reference, show the latest 20 source commits up to the template version applied to your current branch. An update you rendered but have not merged does not advance that boundary.
With a reference, show its complete reachable history. Use a two-dot range to exclude the left endpoint and all its ancestors from the right endpoint's history:
git tpl log main # history through the upstream template branch
git tpl log v2.0.0 # history through a template tag
git tpl log a17b0b2 # history through a template commit
git tpl log ..main # upstream changes absent from the applied version
git tpl log main.. # applied commits absent from upstream main
git tpl log v1.0.0..v2.0.0 # changes between two template versions
git tpl log --max-count 50 # more applied history; -n 50 is equivalent
git tpl log main --all # the complete upstream history
References resolve in the template repository, not your project.
Branches, tags, commit IDs and single-revision expressions such as main~2 are supported.
Omitted range endpoints mean the applied template source revision:
| Argument | History selection |
|---|---|
| none | All history through the applied revision |
REF |
All history through REF |
A..B |
Reachable from B, excluding A and its ancestors |
A.. |
A..applied |
..B |
applied..B |
.. |
applied..applied (empty) |
Three-dot ranges and multiple positional revisions are unsupported. An existing merged rendering with usable provenance is required for every selection. No additional rendering or merge is needed to inspect an available version.
Syntax change: earlier versions treated log REF as applied..REF.
Use log ..REF for that pending-updates view.
Output¶
$ git tpl log ..main
Template: https://github.com/org/rust-template
Applied: v1.0.0 (8b3e7d1)
Target: main (4f2c1a9)
Exclude: v1.0.0 (8b3e7d1)
4f2c1a9 feat(ci): add a release workflow (2 days ago)
a17b0b2 fix!: correct the package layout (1 week ago)
6e8c124 Update installation instructions (2 weeks ago)
Conventional Commit subjects have their type(scope)!: prefix highlighted when color is enabled.
Unknown types and non-conventional subjects are retained in their original order; nothing is grouped or filtered.
The parser recognizes the subject prefix, not breaking-change footers in the commit body.
Hashes are abbreviated for display, and dates use the commit's committer time.
Descendants appear before ancestors, with commit time used to prioritize the walk.
Merge commits and their merged ancestry are included.
Human output goes to stderr and respects --quiet and --color.
Use --json for full commit IDs, subjects, parsed prefixes and absolute timestamps.
Success exits zero, including an empty range or -n 0.
--all and an explicit -n/--max-count are mutually exclusive.
Dates¶
Relative ages are the default, including future ages such as in 2 minutes when source clocks are ahead.
To use absolute dates and times, to the minute:
git tpl log --no-relative-date
git config tpl.log.relativeDate false # this project
git config --global tpl.log.relativeDate false # all projects
Absolute dates use UTC, for example 2026-10-29 14:35 UTC.
The flag overrides the Git configuration setting.
An out-of-range calendar timestamp is displayed as Unix seconds instead.
Date display choices do not change the JSON payload.
Which history is applied?¶
The applied rendering is the newest commit along refs/tpl/<id>'s first-parent history that is reachable from HEAD.
Its provenance identifies the original template repository and source commit.
The log follows that recorded source even if the project configuration has since been edited to name another source.
It does not use the newest unmerged rendering reported by status.
Application is a Git ancestry relationship, not a comparison of file contents.
Squash merges and cherry-picks do not preserve it; reverting files does not remove it.
An attachment made with init --no-merge needs to be merged before it has an applied history.
If the rendered ref is absent, restore the original rendered ref.
Fetching a shared ref alone does not restore the local ref.
Unusable provenance and dirty-worktree renderings are diagnosed rather than replaced with an older guessed baseline.
Commit the template changes, update, and merge a clean rendering to inspect its exact source history.
Ranges use Git's literal two-dot reachability semantics, left..right.
For main.., an upstream main that already contains the applied revision leaves no commits to show.
For ..main, an equal or older main normally leaves no commits to show.
Divergent endpoints show commits reachable only from the right side after excluding the left side's ancestry.
This is not a symmetric difference or a list of removals when downgrading.
Source access and scope¶
A local source is opened in place; a remote source uses the persistent bare source cache. Inspection can require network access to refresh mutable references or obtain missing source objects. Cached source objects remain until cache maintenance removes them. Missing historical source objects, including rewritten history or an incomplete local clone, produce an actionable error.
The project branch, index, worktree, configuration and refs are unchanged.
No manifest is loaded, so history can include commits before template.toml existed or while it was invalid.
No template commands or data sources are run.
This log covers the main template source repository.
It does not combine inherited/composed repositories or explain changes caused by answers or remote data.
For the actual effect on your project, render with update and inspect diff.