GitHub Integration

Version control, collaboration, and automated deployments

How It Works

GitHub integration allows you to push your VibeFactory projects to GitHub repositories. When you connect GitHub to a project:

  • A new repository is automatically created under your GitHub account
  • Your project files are pushed as the initial commit
  • You can view commit history directly in VibeFactory
  • Access your code through GitHub for further development

Repository Connection

When Connected

Once your project is connected to GitHub, you'll see:

Repository Connected

Disconnect

This project is connected to username/repository-name

View commit history below

Commit History

↻ Refresh

username/repository-nameuser-github-username

Initial commit: Add project files from VibeFactory...

👤 username • Just now

Features

Push to GitHub

Export your VibeFactory projects directly to new GitHub repositories with a single click.

Source Code Access

Get full access to your generated code through GitHub repositories for further development.

Version Control

Track changes and maintain version history of your AI-generated applications.

Repository Creation

Automatically create new public or private repositories for your projects.

How to Connect GitHub

Note: GitHub integration is available on all paid plans (Starter and Pro). Connect your GitHub account to enable version control and collaboration features.

1

Navigate to GitHub Settings

In your project, click on the GitHub option in the left sidebar.

2

Connect Your GitHub Account

If not already connected, you'll be prompted to authorize VibeFactory to access your GitHub account.

3

Push to GitHub

Click the push button to create a new repository with your project files. The repository will be named after your project.

What Happens When You Connect:

  • • A new repository is created under your GitHub account
  • • Repository name matches your project name (e.g., generate-hello-world-web-97)
  • • All project files are committed with message "Initial commit: Add project files from VibeFactory..."
  • • The repository link appears in your project settings
  • • Commit history becomes visible in VibeFactory

What You Can Do After Connecting

Access Source Code

Navigate to your GitHub repository to view and download all generated source code files. You can clone the repository locally for further development.

Team Collaboration

Share the repository with your team. Other developers can clone the repo, make changes, and collaborate using standard Git workflows.

Version History

View commit history directly in VibeFactory. Track changes and see when your project was pushed to GitHub.

Local Development

Clone the repository to your local machine, make changes using your favorite IDE, and continue development outside of VibeFactory.

Troubleshooting

GitHub Connection Failed

If you can't connect to GitHub:

  • • Verify you're on a paid plan (Starter or Pro)
  • • Ensure you're logged into the correct GitHub account
  • • Check that you've authorized VibeFactory to access your GitHub
  • • Try disconnecting and reconnecting your GitHub account
Repository Not Created

If the repository wasn't created:

  • • Check if a repository with the same name already exists
  • • Verify you have permissions to create repositories
  • • Ensure your GitHub account isn't at its repository limit
  • • Try refreshing the page and attempting again
Commit History Not Showing

If commit history isn't visible:

  • • Click the Refresh button next to "Commit History"
  • • Verify the repository was successfully created on GitHub
  • • Check your internet connection
  • • Wait a few moments for GitHub to process the push

Best Practices

✅ DO

  • • Commit frequently with descriptive messages
  • • Use branches for features and experiments
  • • Set up branch protection rules for main
  • • Review pull requests before merging

❌ DON'T

  • • Don't commit sensitive data (API keys, passwords)
  • • Don't force push to shared branches
  • • Don't work directly on main branch for large changes
  • • Don't ignore merge conflicts