FAQ
Frequently Asked Questions
Answers to common questions about creating and managing Custy template backups.
custy backupCategory
Quick Command
custy backup allOverviewâ
This page answers common questions about the backup command and explains how backup operations fit into the overall Custy workflow.
What does the backup command actually back up?
The backup command creates timestamped copies of template resources managed by Custy.
Typical backup targets include:
- Commit message templates.
- Tag message templates.
It does not create backups of your entire project or Git repository.
Will backup modify my Git history?
No.
The backup command only creates additional files inside the configured backup directories.
It does not:
- create commits,
- create tags,
- push changes,
- modify repository history.
Any generated backup files remain under your control and may be committed later if you choose.
Should I run backup before editing templates?
Yes.
Creating a backup before editing template files preserves the previous version and provides a convenient recovery point if you later decide to revert your changes.
Although optional, this is the recommended workflow.
Why are backup filenames timestamped?
Timestamped filenames allow multiple versions of the same template to coexist.
Instead of overwriting older backups, Custy preserves previous revisions while applying the configured backup retention policy.
What happens if the template file does not exist?
If the requested template file cannot be found, Custy safely skips that backup operation.
No empty backup file is created.
Depending on the selected backup subcommand, other backup operations may still continue successfully.
Can I change where backups are stored?
Yes.
Backup locations are determined by your project's configuration.
You can customize the backup directories to match your project's preferred layout and organization.
Does Custy remove old backups automatically?
Yes.
Custy manages backup history according to the configured retention policy.
Older backup files may be removed automatically after new backups are created, helping keep backup directories organized.
Can backup operations participate in workflows?
Yes.
Backup operations can be executed directly using the backup command.
They can also participate as workflow stages within larger Custy workflow pipelines.
The Run command documentation explains how workflow stages can be combined into larger automated workflows.
Congratulations!
You have completed the documentation for the custy backup command.
Continue with the remaining command documentation to learn how backup, validation, initialization, versioning, changelog generation, and release workflows work together throughout the Custy ecosystem.