FAQ

🚀Frequently Asked Questions

Support Guide

Find answers about profile selection, changelog generation, composition, pushing, and Full-profile safety.

Commandcusty run

📦Category

Pipeline

🚀Quick Command

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

---

FAQprofilessupport

---

Overview

These answers clarify how public profiles are selected, combined, and bounded.

💡Choose the smallest profile

Prefer a named profile whose effects match the required outcome. More stages do not make a workflow inherently safer.

---

Which Profile Should I Use?

Use dev for daily commit-and-push work, release for a tagged release, and full only when workflow finalization is also intended.

---

Can I Run Only Changelog Generation?

Not through the current Run argument. Use custy changelog generate.

---

Can I Combine Profiles?

Yes, but only from the six accepted names. Custy expands, deduplicates, and globally orders the merged steps.

---

Is `commit tag push` Identical to `release`?

They are closely related after normalization, but the named release profile is the clearer source of truth and may evolve intentionally as one workflow.

---

Does Run Always Push?

No. The commit and tag profiles remain local. push, dev, release, and full contain a push stage.

---

Is `full` Safer Because It Does More Validation?

No profile is automatically appropriate for every repository. full has the broadest effects and also invokes experimental finalization, so it requires the most review.