Skip to main content

First Workflow

Your First Custy Workflow

Preview First

Understand, preview, and deliberately run Custy's development pipeline for the first time.

Commandcusty --dry-run run dev

Category

Getting Started

Quick Command

custy [GLOBAL OPTIONS] run dev [OPTIONS]
Dev profilecommitpush
Profile
dev
Creates Commit
Yes in normal mode
Pushes Remotely
Yes in normal mode
First Invocation
Dry run

Overview​

The public Dev profile coordinates routine development work. Its current registered sequence validates and opens only the commit message, backs it up, stages selected changes, creates a commit, and pushes branch HEAD.

For a first run, use global dry-run mode. Move to normal execution only when the repository, generated resources, commit message, and remote destination have all been reviewed.

Preflight Checklist

Before You Begin

  • Initialization is reviewedRequired

    Project configuration, templates, and version resources exist in the intended locations.

  • Validation succeedsRequired

    custy validate completes without unresolved readiness failures.

  • Working-tree changes are understoodRequired

    Only the files intended for the next commit are present or staged.

  • Commit message is readyRequired

    The configured commit-message file contains a reviewed message for this change.

  • Remote destination is confirmedRequired

    The configured remote is reachable and points to the intended repository.

Review repository state
bash
git status --short --branch
git diff
git diff --staged
git remote -v
custy validate

What the Dev Profile Does

Registered Development Sequence

1
Validate the repository
Confirm that execution starts inside a Git repository.
completed
2
Validate commit and remote inputs
Resolve the commit validator, hook policy, message file, and remote.
completed
3
Review the commit message
Open only the configured commit-message file and validate the saved result.
completed
4
Back up and retain the message
Back up the commit message and clean retained backups.
completed
5
Publish development work
Stage resolved changes, create the commit, and push branch HEAD without pushing a tag.
current

Preview the Workflow

Global options belong before run.

Dry-run the Dev profile
bash
custy --dry-run run dev

Review the output for the resolved commit-message file, backup locations, staging behavior, commit preparation, and remote destination. If any part is unexpected, stop and adjust the project configuration or command options.

Run Normally When Ready

Normal execution is an explicit decision after the preview and repository review.

Run the development profile
bash
custy run dev

After completion, verify both local and remote state.

Post-run verification
bash
git status --short --branch
git log -1 --decorate --oneline
git remote -v

Choose a Different Profile

Common Alternatives

Commit

Use custy commit or the Commit run profile for documented local commit preparation without the Dev profile's final push stage.

Release

Use custy run release only after reviewing version, changelog, commit, tag, and push requirements.

Full

Use custy run full when the release stages and experimental finalization behavior are both intentional.

Direct Commands

Choose a focused command from the command reference when a multi-step pipeline is unnecessary.

Continue

Related Commands

Commands commonly used together with this command.

Dev Profile

Review exact behavior, limitations, and examples.

Run Safety

Understand dry-run boundaries and consequential stages.

Push

Review remote resolution and synchronization behavior.