Features
Publishing to a GitHub + Vercel site
For a site built in a GitHub repository and hosted on Vercel, Nexus publishes each article as a pull request. The piece goes live when someone reviews the Vercel preview and merges.
What it does
For a site built in a GitHub repository and hosted on Vercel, Nexus publishes each article as a pull request. The piece goes live when someone reviews the Vercel preview and merges.
Set it up
- "Connect GitHub for them." Nexus posts an install link for its GitHub app.
- ✋ Someone with access to the client's repository installs it on that repository.
- Tell Nexus which repository to publish to: "Set the git publishing target to owner/name."
- "Check the GitHub connection."
Use it
- "Publish [title] to the site." Nexus opens the pull request and posts the preview link.
- ✋ Review the preview and merge.
- After merging: "[title] is live at [url]." That triggers the social cross-posts.
Troubleshooting
- The message says "Git auth failed." The credential expired or can't see the repository. The message says which.
Prompts
- "Connect GitHub for them."
- "Set the git publishing target to owner/name."
- "Check the GitHub connection."
- "Publish [title] to the site."
- "[title] is live at [url]."
Machine twins: /help/cms-git-vercel.json · /help/cms-git-vercel.md · /help.json · /llms.txt
Reviewed 2026-10-15. In Slack, ask Nexus how do I … and it answers from this guide, with where your company stands.
Related guides
Early access
Put a team on an operating system.
Nexus is rolling out to a first cohort of agencies and go-to-market teams. Tell us about yours and we will be in touch as access opens.
Prefer to tell us more first? Run the two-minute readiness assessment →