`git tpl show`¶

The template's version of one file.

git tpl show [--dirty] <path>

It reads refs/tpl/<id> and writes what it finds to standard output. Nothing else: no header, no colour, no summary line.

$ git tpl show Cargo.toml
[package]
name = "demo"
version = "0.1.0"
license = "MIT"

The moment it exists for is a conflicted merge. The worktree holds the merge markers, HEAD holds your side — and this holds the template's, in one command, without a checkout and without remembering the ref name.

git tpl show src/lib.rs > /tmp/theirs.rs

The plain Git equivalent¶

git show refs/tpl/github-com-noirbizarre-rust-library-template:Cargo.toml

Identical. git tpl show looks up the ref name for you; that is the whole of what it adds.

Reading it¶

Standard output is the file's bytes, verbatim, so it redirects and pipes cleanly. Anything that goes wrong is a diagnostic on standard error and a non-zero exit.

Paths are relative to the repository root, not to your current directory — the same paths git tpl diff --name-only prints.

Directories¶

A path naming a directory lists what is under it, one root-relative path per line, recursively:

$ git tpl show src
src/lib.rs

git tpl show . therefore lists the whole rendering, which is a shorter way of asking what the template actually produces.

Options¶

Option	Meaning
`--dirty`	Read from the template's working tree rather than the rendered ref. Local templates only.
`--answer KEY=VALUE`	Supply an answer for the `--dirty` preview, skipping its prompt. Repeatable.
`--answers-from PATH`	Read those answers from a TOML, JSON or YAML file. Repeatable.
`--defaults`	Accept every default without prompting.
`--strict-answers`	Fail when a supplied answer names no question.

--dirty renders the template's working tree into a commit no ref points at, so you can read one file out of an uncommitted template edit without committing it first. The answer flags apply to that preview only; nothing is recorded and no ref moves. See answers for how they combine.

Without --dirty, it reads the ref and nothing else

show never clones, never fetches and never contacts the network. It reads the rendering that git tpl update already committed, so it works offline and in the middle of a merge. If the ref is not there, run git tpl update — or git tpl fetch, if the template ref is shared, since template refs are never pushed automatically.

--dirty is the one exception: it reads the local template directory, and a template with a network data source may prompt for trust before it renders.

Errors¶

Code	Meaning
`tpl::ops::no_rendered_ref`	`refs/tpl/<id>` does not exist. Run `git tpl update` or `git tpl fetch`.
`tpl::ops::no_such_path`	The path is not in the rendering. `git tpl diff --name-only` lists what is.
`tpl::ops::invalid_argument`	The path was absolute, or left the rendering with `..`.

git tpl show¶