Skip to main content

Everyday Development

Everyday Development

Preview First

Take reviewed working-tree changes through commit-message validation, commit creation, and branch push.

Commandcusty run dev

Category

User Guide

Quick Command

custy --dry-run run dev [OPTIONS]
daily workflowcommitpush
Creates Commit
Yes
Pushes
Yes
Applies Version
No
Creates Tag
No

Goal​

Use the Dev profile when reviewed daily work should create one local commit and finish with a remote branch push. Release artifacts, changelog generation, version changes, and tags remain outside this profile.

Before You Begin

Before You Begin

  • Custy resources existRequired

    The project configuration and commit-message file resolve as intended.

  • The active branch is correctRequired

    The branch shown by Git is the branch you intend to commit and push.

  • Changes are understoodRequired

    Review unstaged and staged differences so unrelated work is not included.

  • The commit message is readyRequired

    The configured commit-message file contains a reviewed message.

  • Remotes are intentionalRequired

    Every configured or selected destination points to the expected repository.

Development preflight
bash
git status --short --branch
git diff
git diff --staged
git remote -v
custy validate

Recommended Journey

Daily Development

1
Review the working tree
Confirm branch, changes, staged state, commit message, and remotes.
completed
2
Preview Dev
Run the complete profile in global dry-run mode and read the resolved files and destinations.
completed
3
Review the intent
Check commit-message editing, backup, staging, commit, and branch-push messages.
completed
4
Execute normally
Run Dev without dry-run only after every reported action is acceptable.
current
5
Verify local and remote state
Inspect the final status and commit, then confirm the destination branch received it.
pending
Preview, then execute
bash
custy --dry-run run dev
custy run dev

What Dev Actually Includes

Profile Effects

Validation

Validate repository, commit-message, hook, and remote readiness.

Commit Message

Open and validate only the configured commit-message file.

Backup and Commit

Back up the commit message, prune retained backups, stage, and commit.

Git Publication

Push branch HEAD to resolved destinations without pushing a tag.

Dev does not prepare or apply versions, initialize a release workflow, generate release artifacts or a changelog, edit a tag message, create a tag, or push a tag. The exact 13-step order explains every internal step.

Verify Completion

Local verification
bash
git status --short --branch
git log -1 --decorate --stat
git tag --points-at HEAD
git remote -v

Expect the intended commit to exist and the working tree to reflect only any deliberately uncommitted work. Dev should not create a new release tag. Confirm the remote result using your repository host or an appropriate Git fetch and comparison workflow.

Continue

Related Commands

Commands commonly used together with this command.