project-deploy-validator

Automated deployment validation checks GitHub CI status, Vercel build readiness, and Supabase migration integrity after a pull request. It automatically attempts to fix common failures once per type and reports the outcome via PR comments or stdout.

Yes, auto-fixing deployment failures attempts to resolve linting errors, type mismatches, and build issues in CI, Vercel, and Supabase migrations. It makes a single auto-fix attempt per failure type and reports the final deployment validation results.

Deployment validation verifies branch deployments by checking if the CI pipeline passed, Vercel deployed successfully, and Supabase migrations applied correctly. It runs automatically after pushing a feature branch to a pull request targeting the development branch.

Yes, deployment validation works with Supabase migrations and Vercel builds alongside GitHub Actions CI. It verifies deployment readiness across these platforms, attempts to auto-fix failures, and reports results through PR comments or stdout for direct pushes.

The limitation of auto-fixing CI/CD pipeline failures is that it attempts only a single fix per failure type for CI, Vercel builds, or Supabase migrations. If the automated fix fails, it reports the deployment validation error without making further attempts.

To validate deployment status for direct development pushes, the validator runs the CI, Vercel, and Supabase checks and reports the results via stdout. This allows you to verify branch deployment readiness without requiring a pull request comment.