Fix GitHub Pages deploy by exporting Next.js build to frontend/out - #1
Merged
Conversation
Rishisharma029
marked this pull request as ready for review
July 31, 2026 14:57
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job build-and-deploy
Fix GitHub Pages deploy by exporting Next.js build to Jul 31, 2026
frontend/out
There was a problem hiding this comment.
🟡 Not ready to approve
output: 'export' is enabled unconditionally, which is incompatible with next start and breaks the repo’s Docker Compose/self-hosted deployment path.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.
Pull request overview
This PR updates the Next.js configuration to produce a static export in frontend/out so the GitHub Pages workflow can upload the expected artifact, while keeping the /api/* proxy rewrites limited to local development.
Changes:
- Enable static export output (
output: 'export') sonpm run buildcan generatefrontend/out. - Move
/api/:path*rewrite configuration behind a development-only guard to avoid export-time route incompatibilities.
File summaries
| File | Description |
|---|---|
| frontend/next.config.js | Enables static export and scopes rewrites to development to support GitHub Pages artifact upload. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.
Comment on lines
2
to
7
| const nextConfig = { | ||
| reactStrictMode: true, | ||
| output: 'export', | ||
| images: { | ||
| domains: ['api.dicebear.com'], | ||
| }, |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
build-and-deployworkflow failed becauseactions/upload-pages-artifactexpects./frontend/out, but the frontend build produced only.next. This PR aligns Next.js output with the deploy workflow artifact path.Build output alignment
frontend/next.config.jssonpm run buildemitsfrontend/out(the directory uploaded by the Pages workflow).Dev-only API proxy behavior
/api/*proxy rewrites, but define them only in development to avoid export-time custom route incompatibilities.Config change (core)