Skip to main content

Overview

Backup Template Files

Recommended

Create backup copies of Custy's commit and tag message templates before modifying them.

Commandcusty backup

Category

Backup

Quick Command

custy backup
backuptemplatesworkflow
Category
Backup
Subcommands
commit, tag, all
Modifies Repository
No Git history changes
Recommended
Before editing templates or preparing releases.

Overview​

The backup command creates backup copies of Custy's template files before they are modified or reused by later workflows.

Rather than backing up an entire project, this command focuses specifically on Custy's generated template resources, allowing previous versions to be restored if needed.

Available Subcommands

Backup Operations

Commit

Backup the configured commit message template.

Tag

Backup the configured tag message template.

All

Backup both commit and tag message templates in a single operation.

What Gets Backed Up?

Custy can create backups for:

  • Commit message templates.
  • Tag message templates.
  • Custom template locations configured in .config/custy/config.toml.

Backup files are written into the configured backup directories using timestamped filenames to preserve previous versions.

When Should I Create Backups?

Creating backups is recommended before:

  • Editing template files.
  • Changing commit conventions.
  • Updating release message formats.
  • Migrating project configuration.
  • Running release workflows.

Although backup is optional, it provides a simple recovery mechanism for template changes.

Related Commands

Commands commonly used together with this command.

init

Generate the template files that can later be backed up.

cleanup

Remove old backup files when they are no longer needed.

run

Workflow commands may use backed-up templates during release operations.