Workflow

🚀Workflow

Recommended

Learn how Custy performs backup operations before later workflow stages.

Commandcusty backup

📦Category

Backup

🚀Quick Command

custy backup all

---

workflowbackuppipeline

---

Overview

The backup command creates timestamped copies of template resources before they are modified or reused.

When executed directly, the command performs only the requested backup operation.

Backup operations may also participate in larger Custy workflows, where they act as one stage in a multi-step pipeline.

---

💡Standalone or Workflow Stage

The backup command can be executed by itself or as part of a larger workflow.

The workflow documentation explains how backup stages are combined with other operations such as commit, tag, and release.

---

Backup Timeline

🕒Backup Pipeline

High-level sequence performed during a backup operation.

1

Resolve Configuration

Determine the effective backup configuration, including template locations and backup directories.

completed

2

Locate Template Files

Locate the requested commit or tag template files before creating backups.

completed

3

Create Backup

Generate timestamped backup copies inside the configured backup directory.

completed

4

Manage Existing Backups

Apply the configured retention policy and remove older backups when necessary.

completed

5

Finish

Report the backup result and make newly created backup files available for later workflow stages.

completed

---

Workflow Stages

1. Resolve Backup Configuration

pending

2. Locate Template Resources

pending

3. Create Timestamped Backup

pending

4. Apply Backup Retention

pending

5. Complete Backup

pending

---

ℹ️Safe Operation

Backup operations create additional files but do not modify Git history.

Any generated backup files can be reviewed before deciding whether to include them in a future commit.

---

Relationship to Workflow Commands

The backup command performs backup operations directly.

Workflow-oriented commands can also include backup stages as part of a larger execution pipeline.

Those workflow combinations are documented in the Run command documentation, where backup is described as one reusable workflow stage rather than an independent command.