Skip to main content

Workflow

Workflow

Recommended

Learn how Custy performs validation before executing workflow operations.

Commandcusty validate

Category

Validation

Quick Command

custy validate
workflowpipelinevalidation

Overview​

Validation is the first stage of nearly every workflow-oriented operation in Custy.

Its purpose is to verify that the project is ready before later stages perform actions such as committing, tagging, pushing, or generating releases.

Validation Timeline

Validation Pipeline

High-level sequence performed during project validation.

1
Resolve Configuration
Load project configuration and determine the effective validation settings.
completed
2
Verify Repository
Ensure that the current directory is a valid Git repository and that the configured remote is available.
completed
3
Verify Project Resources
Check the configured version file together with required commit and tag templates.
completed
4
Verify Repository State
Validate staged changes and other repository conditions required before workflow execution.
completed
5
Finish Validation
Report the validation result and allow later workflow stages to continue when successful.
completed

Workflow Stages

1. Resolve Configuration
pending
2. Validate the Repository
pending
3. Validate Project Resources
pending
4. Validate Repository State
pending
5. Complete Validation
pending

Validation in Larger Workflows

Validation is designed to be reusable.

It can be executed directly using:

  • custy validate

or automatically as part of workflow commands such as:

  • custy run commit
  • custy run tag
  • custy run push
  • custy run release

Using the shared validation stage ensures that every workflow begins with the same set of readiness checks.