Complete Profile Reference
Complete Profile Reference
Lihat setiap resolver profile yang ditentukan Custy, tempat penggunaannya, dan concrete steps hasil expansion.
PIPELINE_PROFILESCategory
Quick Command
profile name -> expanded registered stepsRingkasanâ
PIPELINE_PROFILES adalah complete resolver catalog Custy. Profile merupakan
named step definition, bukan otomatis public CLI value. Sebagian profile
diterima custy run, sebagian dipilih secara internal oleh focused commands,
dan sebagian hanya digunakan untuk menyusun larger profiles.
Profile Catalog
All Resolver Profiles
Step count menggunakan fully expanded profile, termasuk nested validation profiles.
| commit ¡ 17 steps | Public Run + direct command. custy run commit dan custy commit. |
|---|---|
| tag ¡ 13 steps | Public Run + direct command. custy run tag dan custy tag. |
| push ¡ 3 steps | Public Run + direct command. custy run push dan custy push. |
| dev ¡ 13 steps | Public Run. custy run dev daily commit-and-branch-push composition tanpa release side effects. |
| release ¡ 25 steps | Public Run. custy run release complete publication flow. |
| full ¡ 26 steps | Public Run. custy run full Release plus workflow finalization. |
| validate ¡ 10 steps | Direct command. custy validate readiness checks. |
| changelog ¡ 1 step | Direct command. custy changelog generate. |
| apply_version ¡ 5 steps | Direct command. custy version update. |
| backup_commit_message ¡ 1 step | Direct command. custy backup commit. |
| backup_tag_message ¡ 1 step | Direct command. custy backup tag. |
| backup_all ¡ 2 steps | Direct command. custy backup all. |
| cleanup_backups ¡ 1 step | Direct command. custy cleanup backups dan backup part dari custy cleanup all. |
| cleanup_branches ¡ 1 step | Direct command. custy cleanup branches dan branch part dari custy cleanup all. |
| init ¡ 1 step | Direct command. custy init. |
| validate-sub-repo ¡ 1 step | Nested internal. Reusable repository validation prefix. |
| validate-sub-pre-commit ¡ 5 steps | Nested internal. Reusable message-provider dan commit-hook readiness group. |
| validate-sub-pre-tag ¡ 3 steps | Nested internal. Reusable version dan tag-message validation group. |
| validate-sub-pre-push ¡ 1 step | Nested internal. Reusable remote validation prefix. |
| cleanup_all ¡ 2 steps | Defined aggregate. cleanup_backup_step plus cleanup_branches_step. Current custy cleanup all command menjalankan dua focused profiles secara terpisah. |
Exact Public Run Expansions
Daftar berikut adalah concrete step order ketika setiap public profile
di-resolve sendiri. Single-profile resolution mempertahankan declared order.01 ensure_git_repo_step
02 ensure_staged_changes_step
03 ensure_commit_validation_provider_step
04 ensure_commit_hook_policy_step
05 ensure_commit_message_file_step
06 ensure_commit_message_file_exists_step
07 prepare_version_step
08 workflow_init_step
09 generate_artifacts_step
10 edit_files_step
11 validate_edited_step
12 apply_version_step
13 generate_changelog_step
14 backup_commit_message_files_step
15 cleanup_backup_step
16 stage_step
17 commit_step01 ensure_git_repo_step
02 ensure_version_file_step
03 ensure_tag_message_file_step
04 ensure_tag_message_file_exists_step
05 prepare_version_step
06 workflow_init_step
07 prepare_tag_message_step
08 generate_artifacts_step
09 edit_files_step
10 apply_version_step
11 backup_tag_message_files_step
12 cleanup_backup_step
13 tag_step01 ensure_git_repo_step
02 ensure_remote_exists_step
03 push_step01 ensure_git_repo_step
02 ensure_commit_validation_provider_step
03 ensure_commit_hook_policy_step
04 ensure_commit_message_file_step
05 ensure_commit_message_file_exists_step
06 ensure_remote_exists_step
07 edit_files_step (include_tag=false)
08 validate_edited_step
09 backup_commit_message_files_step
10 cleanup_backup_step
11 stage_step
12 commit_step
13 push_step (include_tag=false)01 ensure_git_repo_step
02 ensure_staged_changes_step
03 ensure_commit_validation_provider_step
04 ensure_commit_hook_policy_step
05 ensure_commit_message_file_step
06 ensure_commit_message_file_exists_step
07 ensure_version_file_step
08 ensure_tag_message_file_step
09 ensure_tag_message_file_exists_step
10 ensure_remote_exists_step
11 prepare_version_step
12 workflow_init_step
13 prepare_tag_message_step
14 generate_artifacts_step
15 edit_files_step
16 validate_edited_step
17 apply_version_step
18 generate_changelog_step
19 backup_commit_message_files_step
20 backup_tag_message_files_step
21 cleanup_backup_step
22 stage_step
23 commit_step
24 tag_step
25 push_step01 ensure_git_repo_step
02 ensure_staged_changes_step
03 ensure_commit_validation_provider_step
04 ensure_commit_hook_policy_step
05 ensure_commit_message_file_step
06 ensure_commit_message_file_exists_step
07 ensure_version_file_step
08 ensure_tag_message_file_step
09 ensure_tag_message_file_exists_step
10 ensure_remote_exists_step
11 prepare_version_step
12 workflow_init_step
13 prepare_tag_message_step
14 generate_artifacts_step
15 edit_files_step
16 validate_edited_step
17 apply_version_step
18 generate_changelog_step
19 backup_commit_message_files_step
20 backup_tag_message_files_step
21 cleanup_backup_step
22 stage_step
23 commit_step
24 tag_step
25 push_step
26 finalize_step
Untuk friendly explanation setiap Dev, Release, dan Full step, lanjutkan ke Development Pipeline, Release Pipeline, dan Full Pipeline.
Direct-Command dan Support Expansions
validate â 10 steps
01 ensure_git_repo_step
02 ensure_remote_exists_step
03 ensure_version_file_step
04 ensure_staged_changes_step
05 ensure_commit_validation_provider_step
06 ensure_commit_hook_policy_step
07 ensure_commit_message_file_step
08 ensure_commit_message_file_exists_step
09 ensure_tag_message_file_step
10 ensure_tag_message_file_exists_step
changelog â 1 step
01 generate_changelog_step
apply_version â 5 steps
01 ensure_git_repo_step
02 ensure_version_file_step
03 prepare_version_step
04 prepare_tag_message_step
05 apply_version_stepbackup_commit_message â 1 step
01 backup_commit_message_files_step
backup_tag_message â 1 step
01 backup_tag_message_files_step
backup_all â 2 steps
01 backup_commit_message_files_step
02 backup_tag_message_files_step
cleanup_backups â 1 step
01 cleanup_backup_step
cleanup_branches â 1 step
01 cleanup_branches_step
cleanup_all â 2 steps
01 cleanup_backup_step
02 cleanup_branches_step
init â 1 step
01 Initialization_custy_stepvalidate-sub-repo
01 ensure_git_repo_step
validate-sub-pre-commit
01 ensure_staged_changes_step
02 ensure_commit_validation_provider_step
03 ensure_commit_hook_policy_step
04 ensure_commit_message_file_step
05 ensure_commit_message_file_exists_step
validate-sub-pre-tag
01 ensure_version_file_step
02 ensure_tag_message_file_step
03 ensure_tag_message_file_exists_step
validate-sub-pre-push
01 ensure_remote_exists_step