Pre-Deployment Health Check
Automatically review your code before deployment to avoid failures and save credits.
Pre-Deployment Health Check
This is a handy feature designed to help you use your credits efficiently and ensure your deployment goes smoothly.
The Pre-Deployment Health Check is an automated code review system built directly into Rofy’s deployment interface. It runs before your application is deployed and helps identify potential issues early.
What It Does
The Pre-Deployment Health Check performs an automated analysis of your application code before deployment to detect problems that might cause failures.
Key Features
-
Automated
Runs automatically without requiring manual intervention. -
Pre-emptive
Detects issues before deployment happens. -
Comprehensive
Reviews the codebase for possible deployment blockers. -
Cost-Effective
The check typically costs only 2–3 credits.
How to Interpret Results
After the health check runs, you will see one of the following statuses.
✅ All Green — Passed
Status: READY TO DEPLOY
What this means
- No deployment blockers were found.
- Configuration looks good.
- Dependencies are properly set up.
- Your application is safe to deploy.
Next Steps
- Optionally run Preview to test functionality.
- Click Deploy with confidence.
⚠️ Warnings — Proceed With Caution
Status: WARNINGS FOUND
What this means
- No critical blockers were detected.
- Some improvements are recommended.
- Deployment will likely succeed but could have edge cases in production.
Next Steps
- Review the warnings carefully.
- Decide whether to deploy now or fix the suggested improvements.
- You can ask the agent if the warnings could cause production issues.
❌ Critical Issues Found — Do Not Deploy
Status: DEPLOYMENT BLOCKERS FOUND
What this means
- Critical issues were detected.
- Deployment will likely fail if you proceed.
Next Steps
- Fix each critical issue listed.
- Run the Health Check again.
- Deploy only after all blockers are resolved.
Tip
Running the Pre-Deployment Health Check before deploying can help you:
- Prevent failed deployments
- Save credits
- Catch configuration mistakes early
- Ensure smoother production releases