Output
Output
Learn what information Custy reports after creating template backups.
custy backupCategory
Quick Command
custy backup allOverview​
After completing a backup operation, Custy reports the result of the requested backup together with information about the generated backup files.
Depending on the selected subcommand, one or more template files may be backed up during a single execution.
Typical Output
Command Output
Example output produced after running the command.
Commit Template Backup
The commit message template was backed up successfully.✓ Commit message template found
✓ Backup directory ready
✓ Timestamped backup created
✓ Backup completed successfully
Combined Backup
Both template files were backed up successfully.✓ Commit message template backed up
✓ Tag message template backed up
✓ Backup operation completed
Successful Backup
When a backup completes successfully:
- Backup files are written to the configured backup directory.
- Existing backups remain available unless removed by the retention policy.
- Original template files remain unchanged.
- Git history is not modified.
Successful completion indicates that the requested backup operation finished without errors.
Backup Retention
After creating a new backup, Custy may remove older backup files according to the configured retention policy.
This housekeeping step helps prevent backup directories from growing unnecessarily while preserving recent backup history.
Missing Template Files
If the requested template file does not exist, Custy safely skips that backup operation.
No empty backup file is created.
Depending on the selected subcommand, other backup operations may still continue.
What's Next?
If the backup operation does not complete successfully, continue to the Troubleshooting page for guidance on resolving common backup problems.