Configuration

🚀Configuration

Advanced

Configure tag templates, message backups, version files, strategies, and validation defaults.

Commandcusty tag

📦Category

Git Operations

🚀Quick Command

custy tag [OPTIONS]

---

configurationTOMLversion strategy

---

Overview

Project configuration keeps release strategy and tag-related file locations consistent across contributors. CLI values remain available for one-time overrides.

---

Configuration Groups

📋Tag Profile Configuration

Property	Type	Description	Default	Required
[tool.custy.cli.templates.file]	tag_message	Select the tag-message template used by the profile.	-	No
[tool.custy.cli.templates.directory]	backups_tag	Select the directory used for retained tag-message backups.	-	No
[tool.custy.cli.paths]	version_file	Select the project file that receives the resolved version.	-	No
[tool.custy.cli.versioning]	strategy and bump	Configure the default version strategy and related version inputs.	-	No
[tool.custy.cli.execution]	tag behavior	Configure force_tag and transition-check behavior.	-	No

---

Example Configuration

.config/custy/config.toml

toml

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

[tool.custy.cli.templates.directory]
backups_tag = ".config/custy/templates/backups/tag"

[tool.custy.cli.paths]
version_file = "auto"

[tool.custy.cli.versioning]
strategy = "semver"

---

💡Use shared release inputs

Command-line values take precedence for one invocation. Keep the project-wide strategy and file locations in configuration so every contributor resolves the same release inputs.