Development Pipeline
Development Pipeline
Coordinate commit-message review, a local commit, and a branch push without release preparation.
custy run devCategory
Quick Command
custy run dev [OPTIONS]Overviewâ
Dev is a deliberate daily-development profile. It validates and reviews the
commit message, stages selected changes, creates a commit, and pushes branch
HEAD. It does not prepare release state, generate release artifacts or a
changelog, create a tag, or push a tag.
custy --dry-run run dev
custy run devExact Phase Flow
Dev Profile
Exact Dev Step Order
The internal name is shown so users and contributors can match documentation to logs and source.
| 01 â ensure_git_repo_step | Confirm execution inside a Git repository. |
|---|---|
| 02 â ensure_commit_validation_provider_step | Resolve the configured commit-message validator. |
| 03 â ensure_commit_hook_policy_step | Resolve the configured commit-hook policy. |
| 04 â ensure_commit_message_file_step | Resolve the commit-message file. |
| 05 â ensure_commit_message_file_exists_step | Require the commit-message file before editing. |
| 06 â ensure_remote_exists_step | Validate the resolved push destination. |
| 07 â edit_files_step | Open only the commit-message file for review and editing. |
| 08 â validate_edited_step | Validate the reviewed commit message. |
| 09 â backup_commit_message_files_step | Back up the commit-message file. |
| 10 â cleanup_backup_step | Apply configured backup retention cleanup. |
| 11 â stage_step | Stage the files selected by the workflow. |
| 12 â commit_step | Create the local development commit. |
| 13 â push_step | Push branch HEAD without pushing a tag. |
Before You Run
Before You Begin
- Review repository stateRequired
Confirm the current branch and ensure unrelated work will not be staged.
- Check the commit pathRequired
Verify the configured commit-message file and its reviewed content.
- Confirm the destinationRequired
Review the default or selected remotes because push is part of Dev.
- Use dry-run firstRequired
Inspect planned mutations and remote operations before the normal run.
- Review the resultRequired
Check the diff, commit, and remote branch after completion.
Failure and Retry
If Dev fails before commit, inspect the edited message, backups, and the Git index. If it fails during or after push, verify whether the local commit and any remote updates already completed. Do not rerun the whole profile until that state is understood.