fix(guide-ci): Slack notify must not fail the deploy #9
Reference in New Issue
Block a user
Delete Branch "fix/slack-notify-nonfatal"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Run #4 went red even though the guide deploy succeeded — my Notify Slack step let its own exit status fail the job. Fix:
continue-on-error: true, curl exit never propagates (logs the HTTP code instead), and first-line via param-expansion.Merging this auto-triggers a fresh cd-develop run (workflow path). That run should be GREEN, and the
slack notify HTTP:log line will tell us if the runner reaches Slack (200) or not.The Notify Slack step could fail the whole job (turning a successful deploy red, as just happened). A notification must never fail a deploy: - continue-on-error: true on the step - curl captures HTTP code and never propagates a non-zero exit (|| echo) - logs "slack notify HTTP: <code>" so we can see if the runner reaches Slack - first commit line via ${VAR%%$'\n'*} param-expansion (no head pipe) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>