fix(ci): remove Netlify prod deploy that overwrites devsy.sh#330
Conversation
The deploy-update-metadata job was deploying only desktop update metadata files as the entire production site, wiping the main devsy.sh website content. Remove the job and add a restore workflow to roll back to the last known good deploy.
✅ Deploy Preview for devsydev canceled.
|
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Use the correct /sites/{site_id}/deploys/{deploy_id}/restore endpoint
instead of /deploys/{deploy_id}/restore. Remove unused netlify-cli
install step that added ~20s without being used.
1 participant
Summary
deploy-update-metadatajob from the release workflow — it was deploying only desktop update metadata as the entire production Netlify site, wiping devsy.sh (P0 outage)restore-netlify.ymlworkflow_dispatch to restore the last known good deploy via Netlify APIAfter merge, dispatch the "Restore Netlify Site" workflow to bring devsy.sh back online.