Execution

🚀Execution

Active with Known Mismatch

Set reusable safety, staging, validation, and diagnostic defaults across supported commands.

Command[tool.custy.cli.execution]

📦Category

CLI Configuration

🚀Quick Command

[tool.custy.cli.execution]

---

dry runforcestaging

---

📋

Properties

8

⚠️

Generated Dry Run

false

🌿

Generated Stage Mode

all

❌

Known Mismatch

skip_checks

Properties

📋Properties

Property	Type	Description	Default	Required
dry_run	Boolean	Default global preview state. Read-only discovery continues while intended project-file, editor, Git, and remote mutations are simulated.	false	No
force_commit	Boolean	Default force behavior for direct commit and run commit steps.	false	No
force_tag	Boolean	Default force behavior for direct tag and run tag steps.	false	No
skip_checks	Boolean	Generated plural key. Direct Git-operation and run resolvers currently read singular skip_check, so this is a mismatch.	false	No
no_debug	Boolean	Inverse debug default used by global and experimental workflow resolution.	true	No
auto_stage	Boolean	Automatically stage files in supported commit, validate, and run flows.	false	No
stage_mode	all | update | none | manual	Select all changes, tracked updates only, no automatic staging, or explicit manual staging.	all	No
check_cz	Boolean	Backward-compatible strict override. When true, require Commitizen configuration, the cz executable, and final message validation.	false	No

Conservative shared defaults

toml

[tool.custy.cli.execution]
dry_run = false
force_commit = false
force_tag = false
skip_checks = false
no_debug = true
auto_stage = false
stage_mode = "manual"
check_cz = false

Dry-Run Resolution

Custy resolves dry_run using CLI → configuration → built-in default precedence. An explicit global option therefore overrides this setting.

Override the configured default

bash

# Enable simulation
custy --dry-run run release

# Disable simulation and use normal execution

custy --no-dry-run run release

Read-only discovery and validation may still execute in preview mode. Normal diagnostic logging also remains active and may update the configured log file.

🛡️Force and automatic staging broaden side effects

Keep force settings disabled in shared configuration. Pairing auto_stage = true with stage_mode = "all" can include tracked and untracked changes.

ℹ️Use the provider table for new projects

Configure tool.custy.commit.validation for automatic discovery and explicit fallback behavior. Keep check_cz only when an older configuration or CLI workflow needs the strict boolean override.

⚠️Use the CLI for skip-check behavior

Until skip_checks and skip_check are aligned in the source and generated template, use the explicit command option and verify the displayed plan.

Continue

🚀Related Commands

Commands commonly used together with this command.

Run Safety

Review pipeline-specific safety boundaries.

Commit Options

See staging and force options.

Resolution

Understand the known naming mismatch.