Everything worked.
Then you pushed. Now it's broken.
The fastest path is always the same: roll back first to restore the working site, then debug the change in a branch. Don't debug on a live broken site.
Roll back before you debug
Restore the working version immediately: git revert HEAD --no-edit && git push. Once the site is live again, create a branch to investigate the broken change — never debug on a live broken deploy.
Common causes & fixes
Get the site working again: git revert HEAD --no-edit && git push. Then investigate. Every minute the site is down costs you.
Run git diff HEAD~1 HEAD to see exactly what changed. The bug is in that diff.
Sometimes the deploy environment has different Node/Python versions or missing env vars. Check Actions logs for environment errors.
If you updated a package, the new version may have breaking changes. Pin the version back and re-deploy.
Roll back and investigate:
# Roll back immediately: git revert HEAD --no-edit && git push # See what changed: git diff HEAD~1 HEAD # Check deploy logs: gh run list --limit 3
Clarity before cost. Real help. No runaround.
Text PJ — 858-461-8054