Backup Files

🚀Backup Files

Recommended

Learn which files Custy backs up, where backups are stored, and how they are managed.

Commandcusty backup

📦Category

Backup

🚀Quick Command

custy backup all

---

backuptemplatesfiles

---

Overview

The backup command creates timestamped copies of Custy's template files.

These backups allow previous versions of template resources to be preserved before later workflows update or reuse them.

---

💡Template Backups

The backup command operates on template resources generated by Custy.

It does not create backups of your entire project or Git repository.

---

Supported Backup Types

✨Available Backup Operations

📋Commit Message Template

Creates a timestamped backup of the configured commit message template.

🏷️Tag Message Template

Creates a timestamped backup of the configured tag message template.

📁Combined Backup

Backs up both template files during a single operation.

---

Backup Locations

Backup files are stored in dedicated backup directories configured by your project.

Typical locations include separate directories for:

• Commit message backups.
• Tag message backups.

The exact locations are determined from your project's configuration whenever available.

---

Timestamped Backups

Each backup file receives a timestamp-based filename.

This allows multiple historical versions of the same template to coexist without overwriting previous backups.

For example:

commit-message_20260701_093522.bak.txt
tag-message_20260701_093530.bak.txt

The exact filename depends on the original template name and the time the backup was created.

---

Backup Retention

After creating a new backup, Custy automatically reviews existing backups for the same template.

Older backups may be removed according to the configured backup retention policy.

This helps prevent backup directories from growing indefinitely while still preserving recent history.

---

Missing Files

If a template file does not exist, Custy skips that backup operation instead of creating an empty backup.

This allows backup workflows to continue safely when optional resources are not present.

---

ℹ️No Repository Changes

Creating backups does not modify Git history.

The command only creates additional files inside the configured backup directories.

If desired, those backup files may later be committed using your normal Git workflow.

---

Relationship to Workflows

Backup operations can be executed independently using the backup command.

They can also participate in larger workflow pipelines where backup stages are performed before subsequent operations such as commit, tag, or release.

Those workflow combinations are documented separately in the Run documentation.