Skip to content

chore: retain Render legacy redirect as a separate branch - #14

Closed
souravC01 wants to merge 1 commit into
mainfrom
render-legacy-redirect
Closed

souravC01 wants to merge 1 commit into
mainfrom
render-legacy-redirect

Conversation

@souravC01

Copy link
Copy Markdown
Owner

This branch intentionally remains separate from main because Render uses its Dockerfile and redirect server to forward the legacy address to the Vercel frontend.

This draft PR is being created and closed without merging to clear GitHub's recent-push comparison suggestion. Do not merge its redirect-only container configuration into main, and do not delete the branch used by the Render service.

No code, branch contents, production deployment configuration, or Render service settings are being changed.

@vercel

vercel Bot commented Sep 12, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated
jobhelperguru Error Error Sep 12, 2026 8:23am UTC

@souravC01 souravC01 closed this Sep 12, 2026

This branch had an error being deployed

1 failed deployment
Preview — dc34381f Deployed Sep 12, 2026 by vercel[bot]
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