GitHub Sync
Two-way sync between GenMB and GitHub — push generated code to repos and pull external changes back.
GitHub Sync requires the Pro plan or higher.
How GitHub Sync Works
GitHub Sync provides two-way code synchronization between your GenMB app and a GitHub repository. Push your generated code to GitHub for version control, CI/CD pipelines, or team collaboration. Pull changes made externally back into GenMB to continue building with AI.
- ●Push sends all your project files to a GitHub repository — either a new repo or an existing one.
- ●Pull imports changes from GitHub back into GenMB, creating a new version with the external modifications.
- ●Sync is manual (not automatic) — you control when to push and pull, so there are no surprise overwrites.
- ●Works with public and private repositories on GitHub.
Pro feature
GitHub Sync requires the Pro plan or higher. Free plan users can export their code as a ZIP file and manually upload to GitHub.Setting Up
Connect your GitHub account and select a repository from the app settings panel. The setup process takes less than a minute.
Open GitHub settings
Connect your GitHub account
Choose a repository
Start syncing
Pushing to GitHub
Push your current app code to the connected GitHub repository. All project files are committed and pushed in a single operation, making it easy to keep your repo up to date.
- ●Click "Push to GitHub" in the GitHub panel to send your current code to the connected repo.
- ●GenMB commits all project files with a descriptive commit message including the app name and timestamp.
- ●If the repository is new, GenMB initializes it with a README and your project files.
- ●Subsequent pushes update existing files and add new ones. Files removed from GenMB are not deleted on GitHub.
- ●Push operations do not affect your GenMB version history — they are a separate sync action.
Pulling from GitHub
Pull changes from GitHub to import code modifications made outside GenMB — for example, changes from a team member or a CI/CD pipeline.
- ●Click "Pull from GitHub" to import the latest code from the connected branch.
- ●Pulling creates a new version in GenMB with the imported code.
- ●Files added or modified on GitHub are updated in your GenMB project.
- ●After pulling, you can continue refining the imported code with chat, Visual Editor, or GenMB Code.
Pull operations preserve your existing version history — the import is just a new version on top of your timeline.
Conflict handling
GenMB performs a full overwrite on push. If you have made changes both in GenMB and on GitHub, pull first to import the external changes, resolve any issues in GenMB, then push. There is no automatic merge — the last push wins.Troubleshooting
Common issues and how to resolve them when using GitHub Sync.
- ●Authorization errors — Revoke and re-authorize GenMB in your GitHub settings (Settings → Applications → Authorized OAuth Apps).
- ●Repository not found — Make sure the repository exists and your GitHub account has push access to it.
- ●Permission denied — Verify that the GenMB OAuth app has the required repository permissions (read and write access).
- ●Large files — GitHub has a 100MB file size limit. If your project contains large assets, consider using Git LFS or reducing file sizes.
FAQs
What plan do I need for GitHub Sync?▾
Does pushing to GitHub affect my GenMB app?▾
Can multiple team members use GitHub Sync on the same app?▾
Does GenMB auto-sync with GitHub?▾
Ready to build?
Create your first app for free — no credit card required.