Task Details
The repository has backend pull-request checks in /home/runner/work/simboard/simboard/.github/workflows/backend-ci.yml, but there is no equivalent frontend PR workflow.
This leaves frontend changes without automated pull-request validation even though /home/runner/work/simboard/simboard/frontend/package.json already defines lint, type-check, and ci scripts.
Add a GitHub Actions workflow that runs on pull requests affecting frontend/** and relevant shared config, and validates the frontend with the existing project commands.
Steps to Complete
- Add a frontend CI workflow for pull requests to
main
- Scope triggers to
frontend/** and relevant shared config files
- Install frontend dependencies with pnpm
- Run the existing frontend validation command(s)
- Confirm the workflow appears as a required PR check
Additional Notes
Related evidence:
/home/runner/work/simboard/simboard/frontend/package.json
/home/runner/work/simboard/simboard/.github/workflows/backend-ci.yml
Task Details
The repository has backend pull-request checks in
/home/runner/work/simboard/simboard/.github/workflows/backend-ci.yml, but there is no equivalent frontend PR workflow.This leaves frontend changes without automated pull-request validation even though
/home/runner/work/simboard/simboard/frontend/package.jsonalready defineslint,type-check, andciscripts.Add a GitHub Actions workflow that runs on pull requests affecting
frontend/**and relevant shared config, and validates the frontend with the existing project commands.Steps to Complete
mainfrontend/**and relevant shared config filesAdditional Notes
Related evidence:
/home/runner/work/simboard/simboard/frontend/package.json/home/runner/work/simboard/simboard/.github/workflows/backend-ci.yml