Skip to content
Prev Previous commit
Next Next commit
ci(trigger): fail fast when Trigger.dev secrets are unset
Guard the deploy step so a missing TRIGGER_ACCESS_TOKEN or
TRIGGER_PROJECT_ID exits with a clear message instead of a cryptic
trigger.dev CLI error, matching the DATABASE_URL guard in migrations.yml.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015orsjbLX34FPFGujSK3AQK
  • Loading branch information
TheodoreSpeaks and claude committed Jul 1, 2026
commit d22b025a1270ad0c482e780f7f054c95d035d3af
7 changes: 6 additions & 1 deletion .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -166,7 +166,12 @@ jobs:
env:
TRIGGER_ACCESS_TOKEN: ${{ secrets.TRIGGER_ACCESS_TOKEN }}
TRIGGER_PROJECT_ID: ${{ secrets.TRIGGER_PROJECT_ID }}
Comment thread
cursor[bot] marked this conversation as resolved.
run: bunx trigger.dev@4.4.3 deploy --env preview --branch dev-sim
run: |
if [ -z "$TRIGGER_ACCESS_TOKEN" ] || [ -z "$TRIGGER_PROJECT_ID" ]; then
echo "ERROR: TRIGGER_ACCESS_TOKEN and TRIGGER_PROJECT_ID repo secrets must both be set" >&2
exit 1
Comment thread
cursor[bot] marked this conversation as resolved.
fi
bunx trigger.dev@4.4.3 deploy --env preview --branch dev-sim

# Main/staging: build AMD64 images and push to ECR + GHCR
build-amd64:
Expand Down
Loading