Skip to main content

Public Pipeline Profiles

Public Pipeline Profiles

6 Public Profiles

Choose the smallest supported public profile that reaches your intended Git or release outcome.

Commandcusty run

Category

Pipelines

Quick Command

custy run PROFILE [PROFILE ...] [OPTIONS]
committagpushdevreleasefull
Public Run Profiles
6
Resolver Profiles
20
Prioritized Steps
27
Composition
Supported for public names

Overview​

Profiles package related steps into intentional flows. The three focused profiles create a commit, create a tag, or push. The three composite profiles coordinate broader development and release work. They are the public subset of the larger resolver catalog used throughout Custy's direct commands and nested pipeline definitions.

Public Profiles

Choose by Outcome

Commit

Prepare and edit artifacts, apply version state, generate a changelog, back up the commit message, stage files, and create a local commit. See Commit.

Tag

Prepare version and tag state, edit artifacts, apply the version, back up the tag message, and create a local tag. See Tag.

Push

Validate repository and remote readiness, initialize workflow state, and push HEAD plus an eligible tag. See Push.

Dev

Validate and review the commit message, back it up, commit, and push branch HEAD without release side effects. See Development Pipeline.

Release

Run release validation, apply version state, generate the changelog, commit, tag, and push. See Release Pipeline.

Full

Run the Release sequence and then invoke experimental workflow finalization. See Full Pipeline.

The Complete Resolver Catalog

The 20 definitions in PIPELINE_PROFILES fall into four documentation groups:

  • 6 public Run profiles — commit, tag, push, dev, release, and full.
  • 9 direct-command-only profiles — validation, changelog, version update, backup, cleanup, and initialization profiles selected internally by their focused commands.
  • 4 nested validation profiles — reusable repository, commit, tag, and remote validation groups.
  • 1 defined aggregate — cleanup_all, while the current Cleanup All command invokes the two focused cleanup profiles separately.

Open the Complete Profile Reference for every consumer, step count, and exact expanded sequence.

Practical Selection Rules

  • Choose commit, tag, or push when you need that focused outcome inside the pipeline system.
  • Choose dev for daily commit-and-push work where version application and tag creation are intentionally excluded.
  • Choose release for a complete versioned publication flow.
  • Choose full only when you understand and require the additional branch workflow finalization that runs after push.

Direct Command or Profile?

Use a direct command when you need command-specific inputs or one focused operation. Use a profile when Custy should coordinate the surrounding validation, preparation, artifact, backup, and execution stages. For example, custy changelog generate is the supported focused changelog command; custy run changelog is not a public Run invocation.

Continue

Related Commands

Commands commonly used together with this command.