GitHub Actions

GitHub Actions runs automated workflows from a GitHub repository. I use it to check code changes and support deployments, keeping the workflow configuration next to the application code.

What this portfolio checks

The repository's push workflow runs ESLint, TypeScript checks, unit tests, a production build and Playwright browser tests. Each step checks a different concern: code consistency, type errors, application behavior or the built website.

CI and deployment are separate

This portfolio deploys through Vercel's Git integration. A failed Actions workflow does not automatically block that deployment or a merge: required status checks and deployment conditions must be configured separately. Keeping this distinction clear avoids claiming a release gate that the workflow alone does not provide.

My approach to automation

For Laravel projects such as DigiSpace, automated tests help check changes before release. I put quick checks early in a workflow so failures are easier to diagnose. Deployment automation also needs controlled credentials, useful logs and a recovery plan; running a command on push is only part of the process.