Repository navigation
Refactor CI workflow for clarity and structure - #233
jeniferalaquoke wants to merge 1 commit into
Conversation
Implements an automated Continuous Integration (CI) pipeline using GitHub Actions to maintain code quality and ensure application stability. Automatically installs dependencies and runs backend tests, frontend tests, and frontend production builds whenever changes are pushed to the main branch or submitted through pull requests. Uses Node.js 22, npm dependency caching, isolated jobs, execution time limits, and restricted repository permissions. Also supports manual workflow execution and automatically cancels outdated workflow runs to improve CI efficiency and reliability.
|
@jeniferalaquoke is attempting to deploy a commit to the janani-bn's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Not ready to merge yet. The workflow changes merge cleanly with current main, but current-head CI is awaiting maintainer approval, not failing tests. All three jobs need to pass before merge. This also renames the checks to "Backend Tests", "Frontend Tests" and "Frontend Production Build". If branch protection requires the old names, keep those names or update the required-check settings to match. That compatibility check is still unverified, not a confirmed defect. |
|
Update after CI approval: all three GitHub Actions jobs now pass on this head, and this still merges cleanly after #232. I also verified that main has no branch protection or rules requiring the previous check names, so that compatibility concern is cleared. Still not merging automatically while the separate Vercel status is red: "Authorization required to deploy." This is a deployment-authorization gate, not a test or build failure. The Vercel preview needs authorization, or an explicit decision that this preview check is not required for this PR. No repository or Vercel settings have been changed. |
Implements an automated Continuous Integration (CI) pipeline using GitHub Actions to maintain code quality and ensure application stability. Automatically installs dependencies and runs backend tests, frontend tests, and frontend production builds whenever changes are pushed to the main branch or submitted through pull requests. Uses Node.js 22, npm dependency caching, isolated jobs, execution time limits, and restricted repository permissions. Also supports manual workflow execution and automatically cancels outdated workflow runs to improve CI efficiency and reliability.