You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci: improve pipeline feedback and deploy health - #27
Improve CI feedback and API deployment availability without changing application behavior or database schema.
Changes
Enable NuGet caching in the verify and deploy-api jobs, keyed by app/api/packages.lock.json; locked restore remains enabled.
Upload available Playwright reports and test results as a seven-day artifact when verify fails.
After the Render deploy hook, poll the public API /health endpoint for up to five minutes. Each request is capped at two seconds with eight-second pauses between attempts, keeping the worst case under five minutes.
Document the design, CI behavior, and handoff.
Validation
Passed locally:
npm run lint
npm run typecheck
dotnet format app/api --verify-no-changes --no-restore
npm run build
npm run build:api
npm test (409 passed)
Workflow YAML and structural checks; git diff --check
GitHub Actions has not run on this branch yet and will run on this PR.
Deployment and Limitations
No database migrations, application secrets, or production settings were changed.
deploy-api remains restricted to pushes to main and runs after verify and api-image pass.
/health is a liveness check only. It does not prove the exact requested commit is serving or that the database is ready. This health check runs after a merge to main; no live Render deployment was triggered during local validation.
This repository does not receive automatic reviews because it has fewer than 10 stars.
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: defaults
Review profile: CHILL
Plan: Advanced
Run ID: 2cf90982-6a9d-4f00-a379-386c4a0a4381
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Tip
🎯 Customize your risk assessments
Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.
✅ Automatic approvals, with your rules
Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Improve CI feedback and API deployment availability without changing application behavior or database schema.
Changes
verifyanddeploy-apijobs, keyed byapp/api/packages.lock.json; locked restore remains enabled.verifyfails./healthendpoint for up to five minutes. Each request is capped at two seconds with eight-second pauses between attempts, keeping the worst case under five minutes.Validation
Passed locally:
npm run lintnpm run typecheckdotnet format app/api --verify-no-changes --no-restorenpm run buildnpm run build:apinpm test(409 passed)git diff --checkGitHub Actions has not run on this branch yet and will run on this PR.
Deployment and Limitations
deploy-apiremains restricted to pushes tomainand runs afterverifyandapi-imagepass./healthis a liveness check only. It does not prove the exact requested commit is serving or that the database is ready. This health check runs after a merge tomain; no live Render deployment was triggered during local validation.