FAQ

🚀Frequently Asked Questions

Currently Blocked

Find answers about stability, CI/CD use, Full-profile differences, dry-run, and supported alternatives.

Commandcusty workflow branch

📦Category

Experimental Workflow

🚀Quick Command

custy workflow branch [OPTIONS]

---

FAQexperimentalalternatives

---

Overview

These answers explain why the command is documented but not recommended for production use.

🛡️Experimental and currently blocked

The current application source must be corrected and validated before this interface can provide trustworthy transition results.

---

Is `custy workflow branch` Stable?

No. Custy's own help labels it Experimental/Beta, and the current source has a blocking step-name mismatch.

---

Should It Be Used in CI/CD?

No, not in its current state. Fix and validate the application behavior first, then introduce it gradually with validation-only operation.

---

Is It the Same as `custy run full`?

No. Full includes a registered finalize_step after a complete release. The standalone workflow command constructs its own pipeline and currently requests the unregistered name finalize.

---

Does Dry-Run Make the Current Command Usable?

No. Dry-run changes intended mutation behavior; it does not repair pipeline construction.

---

What Should Users Do Meanwhile?

Use stable direct commands and reviewed Run profiles. Perform branch-policy checks through established Git hosting or team processes until Custy's workflow command is corrected.