Custom Sequences

🚀Custom Profile Sequences

Advanced

Merge supported public profiles into one deduplicated and globally ordered pipeline.

Commandcusty run

📦Category

Pipeline

🚀Quick Command

custy run PROFILE PROFILE [OPTIONS]

---

compositiondeduplicationpipeline order

---

Overview

You may provide more than one of the six public names. Custy's resolver expands every selected profile, removes duplicate step names, and sorts the result using the global pipeline order.

---

Composition Examples

📝Examples

Practical command examples.

Commit and push

Merge preparation, commit, and push stages into one ordered pipeline.

CLI

custy run commit push

Commit, tag, and push

Build a release-like sequence from three public profiles.

CLI

custy run commit tag push

Preview tag and push

Inspect the normalized stages before creating or publishing references.

CLI

custy --dry-run run tag push

---

Normalization Behavior

Input order does not force an unsafe execution order. For example, commit tag push becomes one coherent flow with shared validation and preparation stages executed once, followed by ordered commit, tag, and push stages.

---

⚠️Composition can be broader than expected

Combining profiles takes the union of their stages. Review the equivalent built-in release profile before constructing commit tag push; the built-in profile is usually clearer for team automation.

---

ℹ️Only public names are accepted

Profiles such as validate or changelog cannot be added to a public custom sequence until the Custy argument enum explicitly exposes them.