Template Files

🚀Template Files

Active

Select project-owned inputs for changelog rendering, commits, and annotated tags.

Command[tool.custy.cli.templates.file]

📦Category

Template Configuration

🚀Quick Command

[tool.custy.cli.templates.file]

---

Jinja2commit messagetag message

---

📋

Properties

3

⚙️

Changelog Format

Jinja2

📄

Message Format

Text

✅

Status

Active

Properties

📋Properties

Property	Type	Description	Default	Required
changelog	Path string	Jinja2 layout loaded by changelog rendering.	.config/custy/templates/changelog/changelog.j2	No
commit_message	Path string	Message input used by commit, backup, validate, run, and pending-changelog flows.	.config/custy/templates/commit-message.txt	No
tag_message	Path string	Annotation message used by tag, backup, validate, and run flows.	.config/custy/templates/tag-message.txt	No

Generated paths

toml

[tool.custy.cli.templates.file]
changelog = ".config/custy/templates/changelog/changelog.j2"
commit_message = ".config/custy/templates/commit-message.txt"
tag_message = ".config/custy/templates/tag-message.txt"

⚠️Preserve the changelog context contract

You may redesign the Jinja layout, but keep its documented context API. Generate and review the CHANGELOG.md diff after every structural edit.

ℹ️Reviewed message files are preserved

The artifact step keeps a non-empty commit_message or tag_message file unchanged, then opens it for review. Generated release text is used only when the configured message file is empty or missing in a custom pipeline. Generated fallbacks resolve the project name from pyproject.toml or package.json, with the project-directory name as a generic fallback.

Continue

🚀Related Commands

Commands commonly used together with this command.

Changelog Template Contract

Understand data passed to changelog.j2.

Commit Configuration

See commit-specific message behavior.

Tag Configuration

See tag-specific message behavior.