Workflow (Experimental)

🚀Workflow Commands

Experimental / Currently Blocked

Explore Custy's experimental interface for branch and version transition policy.

Commandcusty workflow

📦Category

Experimental Workflow

🚀Quick Command

custy workflow COMMAND

---

workflow policybranch transitionsexperimental

---

🔄

Category

Experimental Workflow

🚀

Public Subcommands

1

❌

Production Ready

No

⚠️

Known Blocker

Step-name mismatch

Overview

The custy workflow command group is an experimental interface for validating and enforcing branch and version transitions.

🛡️Not production-ready

The current command builds a pipeline step named finalize, while Custy's step registry exposes finalize_step. This source-level mismatch can prevent pipeline construction. Do not rely on this command for release governance until Custy is fixed and the workflow is validated end to end.

---

Available Experimental Command

✨Workflow Interface

🌿Branch Transitions

The workflow branch command accepts branch and version boundaries for validation or enforcement.

⚙️Policy Configuration

Resolve enforcement, transition-checking, and backup synchronization settings from project configuration.

❌Current Blocker

Pipeline construction can fail because the command requests finalize while registration exposes finalize_step.

---

Experimental Warning Preview

Experimental feature warning

Custy identifies workflow transition commands as beta functionality.

---

Related Profiles

The registered finalize_step used by custy run full is a separate execution path and is documented under the Full profile.

🚀Related Commands

Commands commonly used together with this command.

custy workflow branch

Review the accepted experimental interface and known blocker.

custy run full

Use the separate registered finalization path after a complete release.

custy validate

Use the stable validation command for supported repository checks.