GitHub Integration

The GitHub integration lets you connect your Buildorado website project to a GitHub repository. This gives you version control, the ability to edit code in your own IDE, collaborate with other developers, and set up automatic deployments. Changes sync in both directions — edits in Buildorado push to GitHub, and pushes to GitHub deploy to your live site.

Connecting GitHub

Step 1: Authorize GitHub

Before connecting a project, you need to authorize Buildorado to access your GitHub account:

1. Go to the Websites dashboard
2. Click the Connect GitHub button
3. You are redirected to GitHub's OAuth authorization page
4. Review the permissions and click Authorize
5. You are redirected back to Buildorado

Buildorado requests permission to create repositories, read and write code, and manage webhooks. The OAuth token is encrypted and stored securely. You only need to authorize once — the connection works across all your website projects.

Step 2: Connect a Project

Once GitHub is authorized, you can connect any website project to a repository:

1. Open your project in the website builder
2. The GitHub connection option is available in the project settings
3. Choose to create a new repository or connect to an existing one
4. Your project files are committed to the repository

When connecting to a new repository, Buildorado creates it under your GitHub account and pushes all current project files as the initial commit.

Two-Way Sync

The sync between Buildorado and GitHub works in both directions.

Pushing Changes (Buildorado to GitHub)

When you save changes in the Buildorado editor — whether through the AI editor, the code editor, or after a generation — the files are synced to your GitHub repository. The sync status indicator in the top bar shows:

• Synced — All local changes have been pushed to GitHub
• Syncing — A push is in progress
• Ahead — You have local changes that have not been pushed yet
• Behind — The GitHub repository has commits that are not in your local project
• Diverged — Both sides have changes that the other does not have (requires resolution)

Pulling Changes (GitHub to Buildorado)

If you or a collaborator pushes changes directly to the GitHub repository (from a local IDE, GitHub's web editor, or a CI pipeline), you can pull those changes into the Buildorado editor:

1. The sync status shows Behind with the number of new commits
2. Click the sync indicator to open the sync panel
3. Click Pull to fetch the latest changes from GitHub
4. Your project files and live preview update to reflect the pulled changes

Conflict Detection

When both Buildorado and GitHub have changes that the other does not have, the sync status shows Diverged. This happens when:

• You make edits in Buildorado while someone else pushes to the same GitHub repository
• You edit files both in Buildorado and in a local IDE without syncing in between

When a conflict is detected, the sync panel shows a conflict resolution dialog. You can choose to:

• Pull remote changes — Replace your local files with the GitHub version
• Push local changes — Overwrite the GitHub version with your local files

For complex conflicts, it is recommended to pull the remote changes, review the differences in the code editor, and then apply your changes on top.

Auto-Deploy on Push

When your project is both connected to GitHub and published to a Buildorado subdomain, pushes to the repository can trigger automatic deployments.

How It Works

1. You push a commit to the GitHub repository (from any source — local IDE, GitHub web editor, CI pipeline)
2. GitHub sends a webhook notification to Buildorado
3. Buildorado checks if the push includes changes to source files
4. If source files changed, a deploy job is queued automatically
5. The site is rebuilt and the live version is updated

This means you can edit code in VS Code, push to GitHub, and your live site updates automatically — without opening the Buildorado editor at all.

What Triggers a Deploy

Auto-deploy only triggers when source files are modified. Changes to non-source files (like README.md or .gitignore) do not trigger a rebuild.

Use Cases

Collaborate with Developers

Connect your project to GitHub so developers on your team can:

• Clone the repository and edit code in their preferred IDE (VS Code, WebStorm, etc.)
• Submit pull requests for review before changes go live
• Use Git branching for experimental changes

Meanwhile, non-technical team members can continue using the AI editor in Buildorado. Both workflows push to the same repository.

Set Up CI/CD Pipelines

With your code in GitHub, you can add CI/CD workflows:

• Run linting and type checking on every push
• Run automated tests before deployment
• Deploy to additional environments (staging, production) through GitHub Actions

Deploy to External Hosting

Connect your GitHub repository to Vercel, Netlify, or another hosting platform for automatic deployments outside of Buildorado. Every push to GitHub triggers a build on the external platform. This is useful if you want to use Buildorado's AI editor for content changes but host on your own infrastructure.

Backup and Version Control

GitHub serves as a complete backup of your project. Every change is tracked with commit history, so you can:

• View the full history of changes
• Compare any two versions
• Revert to a previous state using Git
• Fork the project for a new website

Disconnecting GitHub

To disconnect a project from GitHub:

1. Open the project settings in the website builder
2. Remove the GitHub repository connection
3. The repository remains on GitHub but is no longer synced with Buildorado

Disconnecting does not delete the GitHub repository or any of its contents. Your project files continue to exist in Buildorado independently.

After disconnecting, files are stored in Buildorado's cloud storage instead of GitHub. You can reconnect to the same or a different repository at any time.