Lewati ke konten utama

Troubleshooting Workflows

Troubleshooting Workflows

Recovery Guide

Periksa partial state, temukan failed boundary, dan pilih smallest safe recovery action.

Commandcusty --debug

Category

User Guide

Quick Command

observe -> inspect state -> correct cause -> recover narrowly -> verify
partial pipelinefilescommittagremote
Failure Behavior
Stop at first raised error
Automatic Rollback
No
Recovery Scope
Last completed boundary
Primary Evidence
Output, logs, Git state

Prinsip Pertama​

Failed Custy pipeline belum tentu untouched pipeline. Earlier steps mungkin sudah generate atau edit files, prune backups, stage changes, membuat commit atau tag, atau update satu atau lebih remotes.

Recovery Method

Diagnosis Sebelum Mengubah State

1
Capture the failure
Simpan failed step name, error code atau message, hint, dan reported destinations.
completed
2
Inspect current state
Periksa files, index, latest commit, tags, branches, backups, dan remotes.
completed
3
Find the last completed boundary
Tentukan durable effects yang sudah tersedia dan later stages yang belum berjalan.
completed
4
Correct the original cause
Perbaiki first validation, configuration, content, Git, authentication, atau remote error.
current
5
Recover narrowly and verify
Gunakan smallest direct command atau manual action untuk menyelesaikan atau reconcile intended state.
pending

Evidence Checklist

Inspect local state
bash
git status --short --branch
git diff
git diff --staged
git log -3 --decorate --stat
git tag --points-at HEAD
git branch --all
git remote -v

Before You Begin

  • Read the first errorRequired

    Later messages dapat merupakan consequences; mulai dari step yang menghasilkan failure.

  • Inspect generated filesRequired

    Periksa version files, editable artifacts, CHANGELOG.md, dan message files.

  • Inspect backupsRequired

    Pastikan new copies dibuat atau older copies dipangkas.

  • Inspect Git objectsRequired

    Tentukan apakah staging, commit, tag, atau branch deletion sudah terjadi.

  • Inspect every destinationRequired

    Untuk multi-remote work, verifikasi setiap remote secara independen.

Pilih Recovery Berdasarkan Last Completed Effect

Common Boundaries

Validation Only

Perbaiki reported prerequisite. Later mutation steps belum berjalan.

Files Changed

Review dan reconcile generated files serta index sebelum menjalankan command lagi.

Commit Exists

Jangan membuat ulang commit yang sama. Tentukan apakah tag atau push merupakan remaining action.

Tag Exists

Verifikasi tag target dan message sebelum memutuskan apakah hanya push yang tersisa.

Some Remotes Succeeded

Perbaiki authentication atau policy untuk failed destinations dan hindari duplicate publication.

Finalization Failed

Release mungkin sudah published. Periksa branch transitions terpisah, bukan rerun Full.

Perbaiki Diagnostic Output

Global options ditempatkan sebelum command group.

Diagnostic invocations
bash
custy --debug run release
custy --log-level DEBUG run dev
custy --debug cleanup brancheses --prefix feature/

Gunakan debug output untuk memahami resolution dan execution, tetapi jangan sertakan secrets, tokens, atau sensitive remote credentials saat membagikan logs.

Escalate Ketika State Tidak Jelas

Berhenti dan minta bantuan teammate atau repository administrator sebelum menghapus commits atau tags, force-pushing, mengubah shared branches, restore remote branches, atau rewrite published release history. Pertahankan logs dan current state saat recovery decision ditinjau.

Lanjutkan

Related Commands

Commands commonly used together with this command.