How to Connect GitHub to Dualite - Dualite - Build products and websites in minutes
How to Connect GitHub to Dualite
Push your Dualite project to GitHub for version control, or import an existing GitHub repo as your starting point. The complete guide to both flows, available on the free Starter plan.
May 8, 2026
1 mins read
Connecting GitHub to Dualite gives you version control, code ownership, and a deploy pipeline for free. The connection is OAuth-based : click "Import from GitHub" on the Dualite homepage, click "Connect with GitHub" in the modal that opens, sign in to GitHub in the secure popup, and authorize Dualite. One OAuth handshake unlocks both flows : (1) importing an existing GitHub repo into Dualite as your starting point, perfect when you have an existing codebase you want to keep building with AI prompts, and (2) pushing a Dualite-built project to GitHub so you can track changes, collaborate, and connect to deploy platforms like Netlify or Vercel. Both flows are available across every plan including the free Starter, and both take under 3 minutes to set up. This guide walks through the full process : how the OAuth connection works, how to import a repo, how to push your Dualite project, and how to keep changes in sync going forward.
Why connect GitHub to Dualite?
A few real reasons people connect GitHub :
- Version control : every change to your Dualite project gets a commit. Roll back if something breaks. See exactly what changed between versions
- Full code ownership : the code lives in your GitHub account, not locked inside a builder platform. You can clone it locally, hand it to a developer, audit it line by line
- Deploy pipeline : platforms like Netlify, Vercel, Cloudflare Pages, and Railway all auto-deploy from GitHub. Connect once, ship every change automatically
- Collaboration : multiple developers can work on the same project. Branch, review, merge : standard GitHub flow
- Bring an existing project into Dualite : if you already have a React or Next.js codebase on GitHub, you can import it into Dualite and continue building with AI prompts on top of your existing code
Dualite supports both directions : pulling code from GitHub into Dualite, and pushing Dualite changes back out to GitHub. A single GitHub OAuth authorization unlocks both.
What are the two flows: import vs push?
It's worth understanding the difference upfront because they're used for different things :
- Import flow : you have a GitHub repo with existing code, and you want to use it as the starting point for a Dualite project. Dualite reads your repo, sets up the project, and lets you continue building with AI prompts on top of the existing codebase.
- Push flow : you have a Dualite project, and you want a GitHub repo of it for version control, deployment, or collaboration. Dualite creates (or syncs to) a GitHub repo and keeps it in sync as you continue prompting.
You can do both on the same project : import from GitHub, then push back changes you make in Dualite. The two flows are not mutually exclusive, and the same OAuth grant covers both.
What do you need before you start?
Quick prerequisites :
- A GitHub account (free at github.com)
- A Dualite account (free Starter plan is fine for both flows)
- For the import flow : a GitHub repo with code in it (preferably React, Next.js, or a similar modern web stack)
- For the push flow : a Dualite project you want to push (existing or brand-new)
- About 3 minutes
Notice what's not required : you don't need a personal access token, you don't need to set up SSH keys, and you don't need to copy any URLs. Dualite uses GitHub's official OAuth, which means you sign in to GitHub once and get scoped access to your repos.
Flow 1 : How do you import a GitHub repo into Dualite?
Importing is the path you'll take if you already have code on GitHub and want to continue building with AI prompts on top of it.
Open the Dualite homepage. You'll see the prompt input area with the question "What should we build today?" and below it three connection buttons : Import from Figma, Connect to Cloud, and Import from GitHub.
Click Import from GitHub (the rightmost button, with the GitHub octocat icon). A modal opens titled "IMPORT CODE FROM A GITHUB REPOSITORY" with the message "Please connect with GitHub to use repository features" and a black Connect with GitHub button.
If you've already authorized GitHub in a previous Dualite session, this step is skipped : you'll go straight to the repo selection screen. If this is your first time, click Connect with GitHub.
How does the GitHub authorization work?
Clicking Connect with GitHub opens a new browser tab with GitHub's OAuth authorization screen. You'll see a Dualite logo and the text "Sign in to GitHub to continue to Dualite" with a username/email field. From there :
- If you're not already logged in to GitHub, sign in with your GitHub username/email and password (or your usual two-factor flow)
- GitHub then shows you the permissions Dualite is requesting : access to your repositories, ability to read and write to selected repos, and basic profile info
- You can choose to grant access to all repositories (current and future) or only select repositories : the second option is more restrictive and recommended if you only need Dualite to touch a few repos
- Click Authorize Dualite (or the equivalent confirmation button)
- The authorization tab closes automatically and you're back in Dualite, now connected to your GitHub account
Authorization is one-time per GitHub account. The same OAuth grant covers both the import flow and the push flow, so you only do this once for everything.
How do you pick a repo to import?
After authorization, Dualite shows you a list of GitHub repositories your account has access to. From here :
- Pick the repository you want to import from the list
- Choose which branch to import from (defaults to main)
- Click Import
Dualite reads the repo, sets up the project, and shows you a live preview. From there, you can keep building with prompts : the AI now has full context of the existing codebase and can extend it. Add new pages, refactor existing components, integrate Supabase, anything you'd normally prompt for.
What happens after you import a GitHub repo?
A few things to know about post-import behavior :
- The original repo stays untouched until you push back : importing creates a local Dualite working copy. Changes you make in Dualite don't automatically modify the original GitHub repo unless you push them back (covered in Flow 2)
- Dualite parses the codebase to understand what's there : the AI reads your file structure, components, dependencies, and code patterns so future prompts respect what's already in the project. This means new code gets generated in your existing style, not a generic Dualite default
- Dependencies are preserved : if your repo has a package.json, Dualite installs and respects those dependencies. You can prompt for new dependencies and Dualite will add them too
- Best results come from React, Next.js, or Vite-based projects : Dualite's AI is most fluent in these stacks. Other stacks (Vue, Svelte, plain HTML) work but the prompt quality varies
Flow 2 : How do you push a Dualite project to GitHub?
Pushing is the path you'll take if you started in Dualite and want a GitHub repo of your project for version control or deployment.
Open your Dualite project. Find the GitHub option in the project menu. If you've already done the GitHub OAuth flow during a previous import, you're already authorized : skip ahead. If not, the same Connect with GitHub flow described above applies : modal → Connect with GitHub button → GitHub OAuth screen → Authorize Dualite.
Once authorized, you have two options :
- Create a new GitHub repository : Dualite creates a fresh repo in your GitHub account, named after your Dualite project, and pushes the current project state as the initial commit. Choose public or private at this point
- Connect to an existing repository : pick an empty repo (or one you don't mind overwriting) from your GitHub account and Dualite pushes the project there
Once connected, every meaningful change you make in Dualite from that point forward gets committed back to your GitHub repo. You'll see commits with descriptive messages reflecting what the AI built : useful for reviewing what changed and when.
How do you keep changes in sync after pushing?
Once a Dualite project is connected to GitHub, sync is mostly automatic. Here's how it works in practice :
- Dualite → GitHub : every significant change gets pushed automatically. You can see commit history in your GitHub repo's commits view
- GitHub → Dualite : if you (or a collaborator) push commits to GitHub directly (from a local clone or another tool), Dualite pulls those changes when you reopen the project. The AI sees the new code and respects it for future prompts
- Branch support : work on a branch in Dualite, push it to GitHub, open a pull request, review, merge. Standard GitHub flow with Dualite as one of the contributors
If you ever want to disconnect : there's a disconnect option in the same GitHub menu in Dualite. The repo stays on GitHub : only the live sync is removed.
What are common issues, and how do you fix them?
A few things that come up with the OAuth connection flow :
- Sign-in popup is blocked by your browser : some browsers block automatic popup windows. If clicking "Connect with GitHub" doesn't open a new tab, check for a blocked-popup notification in your address bar and allow popups for the Dualite domain
- OAuth authorization failed or was denied : if you accidentally clicked Cancel instead of Authorize on GitHub's permissions page, just click Import from GitHub again in Dualite and run through the flow once more
- Dualite can't see your repos after authorization : if you chose "Only select repositories" during OAuth and the repo you wanted isn't in the list, go to GitHub Settings → Applications → Authorized OAuth Apps (or Installed GitHub Apps), find Dualite, and update the repo access. Add the specific repo you want or switch to All repositories
- Repo too large to import : extremely large repos (hundreds of files, multiple gigabytes) may have issues. Try importing a smaller subdirectory first or filing feedback on the Dualite support channels
- Branch conflicts : if you push from a local clone while Dualite is also pushing, you can get merge conflicts. Resolve them on GitHub or pull the latest changes into Dualite before continuing
- Imported code looks different from original : Dualite may slightly format the code (whitespace, import order) on first import. The functionality stays the same. If this is a problem, prompt the AI to keep formatting unchanged
Frequently asked questions
Is GitHub integration free on Dualite?
Yes : GitHub import and push are available across every Dualite plan including the free Starter plan. There's no extra cost for connecting GitHub or for syncing changes back and forth.
Does Dualite need my GitHub password?
No. The OAuth flow means Dualite never sees your GitHub password. You sign in directly on GitHub's domain, GitHub issues Dualite a scoped access token, and the token is what Dualite uses to read and write to the repos you authorized. Your password stays with GitHub.
What permissions does Dualite request from GitHub?
Dualite requests scoped repository access : the ability to read your repositories (so it can import code) and write to repositories you authorize (so it can push commits back). You can choose to grant access to all your repos or only specific ones during the OAuth flow. Dualite does not request access to your private organizations, your billing settings, or anything outside the repos you select.
Can I import private GitHub repos?
Yes : during the OAuth authorization, you can grant Dualite access to private repos in your GitHub account. The repos remain private : Dualite doesn't expose them to anyone else.
How do I revoke Dualite's access to my GitHub account?
Two ways : (1) revoke from GitHub directly by going to GitHub Settings → Applications → Authorized OAuth Apps (or Installed GitHub Apps), finding Dualite, and clicking Revoke, or (2) disconnect from Dualite's settings on your project. Option (1) fully removes the OAuth grant on GitHub's side. The next time you click Import from GitHub in Dualite, you'll need to authorize again.
What stack does Dualite work best with on GitHub imports?
React, Next.js, and Vite-based projects with TypeScript and Tailwind CSS work best. The AI models are most fluent in these stacks, so prompts produce cleaner output. Other stacks (plain HTML, Vue, Svelte) work too but with more variation.
Can I use multiple GitHub accounts with Dualite?
You authorize one GitHub account at a time. To switch, revoke Dualite's access from the current GitHub account (via GitHub Settings) and run the Connect with GitHub flow again from a different GitHub account. Useful if you have separate personal and work GitHub accounts.
Does Dualite support GitHub Actions or CI/CD workflows?
Yes : your repo on GitHub keeps any GitHub Actions workflows you've set up. Dualite doesn't modify these. So you can have CI/CD running on every commit Dualite pushes : useful for tests, deployments, and code quality checks.
What happens to my GitHub repo if I delete the Dualite project?
The GitHub repo stays exactly where it is. Deleting a Dualite project only removes Dualite's working copy : the GitHub repo is owned by your GitHub account and continues to exist with all its commit history. You can later import the repo back into a new Dualite project if needed.
Can I work on the same project from Dualite and from a local clone?
Yes : that's one of the main reasons to connect GitHub. You can pull the repo locally, edit in VS Code or any other tool, push back to GitHub, and Dualite picks up your changes. The standard GitHub flow works as expected.
Can I prompt Dualite in any language to push to GitHub?
Yes : the GitHub integration works the same regardless of the language you've set Dualite's interface to (English, Portuguese, Turkish, Russian, or any other supported language). Prompts in your native language work the same way.
Ready to own your code?
Sign up for Dualite's free Starter plan and connect GitHub in under 3 minutes : import an existing repo or push a brand-new Dualite project. Full code ownership, version control, and deploy-ready integration on every plan, including the free Starter. No credit card. 5 free messages to get started.