Pipeline Profiles

🚀Pipeline Profiles

20 Resolver Profiles

Distinguish supported public Run names from profiles used by direct commands and internal composition.

Commandcusty run PROFILE [PROFILE ...]

📦Category

Reference

🚀Quick Command

profile names -> expanded registered steps -> sequential execution

---

6 public names20 resolver profiles27 priorities

---

💻

Public Run Names

6

🪄

Resolver Profiles

20

🕒

Priority Entries

27

🔄

Execution

Sequential

Public Run Profiles

ℹ️Accepted Typed Values

Counts are fully expanded concrete steps for one profile.

commit - 16 steps	Prepare artifacts, validate and edit the commit message, update project state, generate changelog content, back up, stage, and commit.
tag - 13 steps	Validate version and tag-message inputs, prepare artifacts, apply the version, back up, and create a local tag.
push - 4 steps	Validate repository and remote state, initialize workflow context, and push resolved refs.
dev - 12 steps	Run the prepared daily development commit-and-push flow.
release - 24 steps	Run complete validation, version, artifact, changelog, backup, commit, tag, and push behavior.
full - 25 steps	Run Release and then the currently experimental finalization step.

Public examples

bash

custy --dry-run run dev
custy --dry-run run release
custy --dry-run run full

# Supported manual composition

custy --dry-run run commit tag push

---

Other Resolver Profiles

ℹ️Not Additional Public Run Values

Direct-command profiles	validate, changelog, apply_version, backup_commit_message, backup_tag_message, backup_all, cleanup_backups, cleanup_branches, and init.
Nested validation profiles	validate-sub-repo, validate-sub-pre-commit, validate-sub-pre-tag, and validate-sub-pre-push.
Defined cleanup aggregate	cleanup_all exists in the resolver catalog, while the public cleanup-all command currently invokes the two focused cleanup profiles separately.

🛡️Resolver name does not mean public Run value

For example, validate is a real profile used by custy validate, but the typed Run argument does not accept custy run validate.

---

Resolution and Ordering Rules

• Resolving one profile preserves its declared expanded order.
• Resolving multiple profiles expands nested definitions, removes duplicate step names, and performs a stable sort by STEP_ORDER priority.
• A missing priority receives fallback value 999 and therefore moves behind explicitly prioritized built-in steps.
• Cyclic nested profiles and unknown names fail resolution.
• Duplicate public arguments are rejected by the CLI validator.
• Execution stops on the first failing step and does not roll back earlier successful side effects.

---

⚠️Full includes experimental finalization

The full value is accepted publicly, but its additional finalization step uses evolving workflow behavior. Prefer release unless that final phase is specifically required and has been reviewed in a disposable environment.

---

Continue

🚀Related Commands

Commands commonly used together with this command.

Complete Profile Reference

Inspect every resolver profile and exact concrete sequence.

Step Priority

Review all 28 priority entries and merged-profile ordering.

Run Command

Use public syntax, options, profiles, safety, and troubleshooting.

Pipeline Architecture

Trace resolution through registry, builder, context, and execution.