Skip to main content

Development Pipeline

Development Pipeline

Stable

Coordinate commit-message review, a local commit, and a branch push without release preparation.

Commandcusty run dev

Category

Pipeline Profile

Quick Command

custy run dev [OPTIONS]

daily developmentcommitpush

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.

Preview before normal execution
bash
custy --dry-run run dev
custy run dev

Exact Phase Flow

Dev Profile

1
Validate repository
Confirm that execution is inside a Git repository.
completed
2
Validate commit and remote inputs
Resolve the commit-validation provider, hook policy, commit-message file, and remote.
completed
3
Review the commit message
Open only the commit-message file and validate its saved content.
completed
4
Back up and clean
Back up the commit-message file and apply backup retention cleanup.
completed
5
Stage and commit
Stage the resolved project changes and create a local commit.
completed
6
Push
Push branch HEAD to the resolved remotes without publishing a tag.
current

Exact Dev Step Order

The internal name is shown so users and contributors can match documentation to logs and source.

01 — ensure_git_repo_stepConfirm execution inside a Git repository.
02 — ensure_commit_validation_provider_stepResolve the configured commit-message validator.
03 — ensure_commit_hook_policy_stepResolve the configured commit-hook policy.
04 — ensure_commit_message_file_stepResolve the commit-message file.
05 — ensure_commit_message_file_exists_stepRequire the commit-message file before editing.
06 — ensure_remote_exists_stepValidate the resolved push destination.
07 — edit_files_stepOpen only the commit-message file for review and editing.
08 — validate_edited_stepValidate the reviewed commit message.
09 — backup_commit_message_files_stepBack up the commit-message file.
10 — cleanup_backup_stepApply configured backup retention cleanup.
11 — stage_stepStage the files selected by the workflow.
12 — commit_stepCreate the local development commit.
13 — push_stepPush 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.


Continue