Workflow Branch Troubleshooting

Known Blocker

Identify the known finalize-step mismatch and resolve secondary interface, tag-format, enforcement, or backup questions.

Commandcusty workflow branch

Quick Command

custy workflow branch [OPTIONS]

troubleshootingfinalize_stepexperimental

Overview

The step-name mismatch is an application blocker, not a project-configuration problem. Correct and validate the implementation before diagnosing later transition behavior.

An Unknown `finalize` Step Is Reported

This is the known source mismatch. It requires an application fix, not a configuration change.

`--check-transition` Is Rejected

Use the currently declared --check_transition spelling or its -ct short form.

A Tag Override Is Rejected

Use the current shared explicit-tag shape: vX.Y.Z. The validator normalizes a missing v, but it does not accept broader generated prerelease or PEP 440 forms on this option.

Enforcement Behavior Is Unclear

Do not enable enforcement. Review [tool.custy.cli.workflow], test validation in a disposable repository after the implementation is fixed, and document the team's allowed transitions first.

Backup Synchronization Is Skipped

Inspect configuration, branch eligibility, remotes, and dry-run diagnostics. Do not assume a backup occurred without a clear success result.

Overview​

An Unknown finalize Step Is Reported​

--check-transition Is Rejected​

A Tag Override Is Rejected​

Enforcement Behavior Is Unclear​

Backup Synchronization Is Skipped​