Profiles

🚀Public Profiles

Stable with Limitations

Compare the six profile names accepted by the current public Run argument.

Commandcusty run

📦Category

Pipeline

🚀Quick Command

custy run PROFILE [PROFILE ...] [OPTIONS]

---

profilespipeline selectioncomparison

---

Overview

Each accepted name expands to an intentional ordered stage list. Choose the smallest profile that reaches the required outcome.

---

Available Profiles

✨Public Run Profiles

🌿Commit

Prepare artifacts, update version and changelog, back up, stage, and commit. See the Commit guide.

🏷️Tag

Prepare version and tag artifacts, back up, and create a local tag. See the Tag guide.

🌐Push

Validate and push current HEAD plus an optional tag. See the Push guide.

▶️Dev

Validate and review the commit message, back it up, commit, and push branch HEAD without release side effects. See the Dev guide.

🪄Release

Validate, prepare, apply version, generate the changelog, commit, tag, and push. See the Release guide.

🔄Full

Run Release and then finalize workflow state. See the Full guide.

---

ℹ️Profile names are not raw steps

Each name expands to a complete intentional flow. commit, for example, contains validation, version, artifact, changelog, backup, cleanup, staging, and commit stages.

---

Internal Profiles

Internal profiles remain available to Custy's resolver and other commands but are not accepted by the current typed public Run argument.