Deployment recovery brief

ForgeSomero

The application is built and landed on dev. Vercel cannot create the production project until its ForgeBot account gains a GitHub Login Connection.

10/10Tests passed
PASSTypecheck
PASSProduction build
2Requested domains

Current blocker

BLOCKED — Vercel GitHub connection
Vercel returns: “To link a GitHub repository, you need to install the GitHub integration first.” The API credentials can read the ForgeFX team but cannot connect adamkane/forgeapps. No incomplete Vercel project was created.

Already complete

  • Source: apps/forgesomero, based on apps/example
  • Identity: ForgeSomero branding and port 4077
  • Git: pushed and synchronized on dev
  • Validation: tests, TypeScript, and Vite build passed

Still pending

  • Create Vercel project forgesomero with the GitHub link
  • Assign forgesomero.forgefx.dev
  • Assign somero.forgefx.dev
  • Deploy production and verify both routes

Adam’s fix

  1. In Chrome, click Allow on the “Allow remote debugging?” popup. This lets ForgeBot use the already-authenticated Vercel dashboard.
  2. If Vercel still refuses GitHub access, open Vercel Account Settings → Authentication and add GitHub as a Login Connection for the ffx-forgebot account.
  3. Confirm the Vercel GitHub app can access the private adamkane/forgeapps repository.
  4. Reply go in Slack. ForgeBot will create the project atomically, assign both domains, deploy from GitHub, and verify the exact live content.