GitHub integration
GitHub holds the Git repository behind an Astro or Next.js site. Every change goes through a pull request, Vercel, Netlify or Cloudflare build it on each push, and GitHub Actions can run checks before anything is merged. Framer sites can’t be exported to code; Webflow connects through Webflow Cloud and DevLink Export.
| Complexity | Low |
|---|---|
| Method |
|
| Typical setup | 2 to 4 hours |
| What we do | We set up the repo in your organization, branch protection, the host connection with previews and the checks on every pull request. |
| Category | Hosting |
Setup by platform
How we set up GitHub
Framer
- Not supported
Framer doesn’t export published sites as HTML or source code, so a Framer site can’t live in a repo. Coded parts of the project, like an app or docs on a subdomain, can.
Webflow
- Native
The Webflow site itself isn’t stored in Git. Webflow Cloud apps deploy from a GitHub repo on every push, and DevLink Export pulls Webflow components into a React codebase in that repo.
Webflow developmentAstro
- Native
The whole site is code in the repo. We connect it to Vercel, Netlify or Cloudflare, which build on every push to main and give each pull request its own build.
Astro developmentNext.js
- Native
Same flow as Astro. Vercel deploys every push and comments a preview URL on each pull request; Netlify builds a Deploy Preview for every pull request.
Next.js development
Use cases
What teams use it for
Review every change
Each edit is a pull request with a diff and comments. With main protected, nothing ships without an approval.
Preview links per branch
The host posts a preview URL on the pull request, so your team checks the real page before it goes live.
Edits by your team or AI agents
Editors and coding agents, such as GitHub’s Copilot cloud agent, work on a branch and open a pull request that goes through the same review.
Before you add it
What to watch out for
Security
Secrets stay out of the repo
API keys live in the host’s environment variables or in GitHub Actions secrets, never in committed files. Vercel asks for approval before building pull requests from forks, so those values don’t leak.
Limits
Protect the main branch
Branch protection can require a pull request, approving reviews and passing status checks before a merge. Limiting who can push to a private repo needs GitHub Team or Enterprise Cloud.
Data layer
Your organization owns the repo
We create the repo in your GitHub organization, or transfer ours at handover. Issues, pull requests, secrets and webhooks move with it, and old links redirect.
FAQ
Questions about GitHub
Can we keep our Framer site in GitHub?
No. Framer doesn’t export published sites as HTML or source code. If the site needs to live in a repo, that’s a move to Astro or Next.js, which we run as a migration.
Can our Webflow components end up in a React codebase?
Yes. DevLink Export pulls Webflow components into a React project with their props, styles and component interactions, and you rerun it from the CLI when the design changes.
It needs a paid Workspace plan or a CMS, Business or Ecommerce Site plan. CMS-bound content, Ecommerce elements and page-level interactions don’t export.
Should the repo sit in our GitHub organization or yours?
Yours, so the code stays with you whoever builds it. We join as organization members with access to the repo. Vercel needs that: an outside collaborator can’t connect an organization’s repo to a Vercel project.
You've reached the end, so now…
Tell us what you’re building.
We’ll help you map the right scope, team, timeline, and next steps.
Book a call