Skip to content

resolve GitHub Pages build failure #11

Open
motunrayokoyejo wants to merge 1 commit into
mainfrom
resolve-ci-build-error
Open

resolve GitHub Pages build failure #11
motunrayokoyejo wants to merge 1 commit into
mainfrom
resolve-ci-build-error

Conversation

@motunrayokoyejo
Copy link
Copy Markdown
Contributor

@motunrayokoyejo motunrayokoyejo commented May 19, 2026

Fixes the GitHub Actions deploy workflow so next build succeeds when publishing to GitHub Pages.


Note

Low Risk
Low risk: workflow-only environment flag plus a conditional Sentry config tweak; main impact is disabling the /monitoring tunnel route specifically for GitHub Pages builds.

Overview
Fixes GitHub Pages deploy builds by setting GITHUB_PAGES=true during the next build step and using it in next.config.js to skip Sentry tunnelRoute configuration (which relies on rewrites unsupported by Pages static export).

Non-Pages builds keep the existing Sentry tunnel behavior; Pages builds proceed with next export without attempting the rewrite-based tunnel.

Reviewed by Cursor Bugbot for commit 35d6c63. Bugbot is set up for automated code reviews on this repo. Configure here.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 19, 2026

Deploy Preview for convoy-playground ready!

Name Link
🔨 Latest commit 35d6c63
🔍 Latest deploy log https://app.netlify.com/projects/convoy-playground/deploys/6a0c0d05f7e42300082aa9d9
😎 Deploy Preview https://deploy-preview-11--convoy-playground.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 19, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
convoy-playground Ready Ready Preview, Comment May 19, 2026 7:11am

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 35d6c63. Configure here.

Comment thread .github/workflows/nextjs.yml
- name: Build with Next.js
run: ${{ steps.detect-package-manager.outputs.runner }} next build
env:
GITHUB_PAGES: true
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reserved GITHUB_ prefix renders env var ineffective

High Severity

GITHUB_PAGES starts with the GITHUB_ prefix, which is reserved by GitHub Actions — custom env vars with this prefix cannot be set or overwritten in a workflow step. The env: GITHUB_PAGES: true assignment will be silently ignored, so process.env.GITHUB_PAGES will never equal 'true' in next.config.js. As a result, isGithubPagesBuild is always false, tunnelRoute: '/monitoring' is always included, and the build failure this PR intends to fix will persist.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 35d6c63. Configure here.

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.

1 participant