Skip to content

Fix Pages build job to use the actual frontend project paths - #1

Draft
orcadevstack with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-github-actions-build-job
Draft

Fix Pages build job to use the actual frontend project paths#1
orcadevstack with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-github-actions-build-job

Conversation

Copilot AI commented Aug 13, 2026

Copy link
Copy Markdown

The GitHub Actions build job failed before install/build because setup-node was configured with a non-existent lockfile path under webapp. This PR aligns the workflow with the real Next.js project location in app.

  • Root cause addressed

    • cache-dependency-path referenced webapp/package-lock.json, which is absent.
    • Job default working directory and artifact upload path were also pointed at webapp, while the built frontend lives in app.
  • Workflow path alignment

    • Updated build job working-directory from webapp to app.
    • Updated npm cache lockfile path from webapp/package-lock.json to app/package-lock.json.
    • Updated Pages artifact path from webapp/out to app/out.
  • Representative diff

    defaults:
      run:
        working-directory: app
    
    - uses: actions/setup-node@v4
      with:
        node-version: 20
        cache: npm
        cache-dependency-path: app/package-lock.json
    
    - uses: actions/upload-pages-artifact@v3
      with:
        path: app/out

Copilot AI changed the title [WIP] Fix failing GitHub Actions job build Fix Pages build job to use the actual frontend project paths Aug 13, 2026
Copilot AI requested a review from orcadevstack August 13, 2026 23:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants