Overview
VibeHub is built around familiar version control concepts, enhanced for AI-native development. If you’ve used Git or GitHub before, you’ll feel right at home.Projects
A project is the top-level container for your code. It’s similar to a repository in Git. Each project contains:- Commits - Snapshots of your code at different points in time
- Branches - Parallel lines of development
- Files - Your actual source code and assets
- Collaborators - Team members who can access the project
Projects can be public (anyone can view) or private (only collaborators can access).
Commits
A commit represents a snapshot of your project at a specific point in time. In VibeHub, commits are special because they can capture more than just code changes.What’s in a Commit?
| Component | Description |
|---|---|
| Message | A description of what changed |
| Files | The actual code changes (additions, modifications, deletions) |
| Author | Who made the commit |
| Timestamp | When the commit was made |
| Prompts | AI prompts that were used during development (optional) |
| Parent | The commit this one builds upon |
Prompt-Native Commits
What makes VibeHub unique is the ability to capture AI prompts alongside your code. When you use AI tools like Cursor or Claude during development, VibeHub can record those conversations and link them to your commits. This means you can:- See exactly what prompts generated specific code
- Learn from how AI was used in past development
- Provide better context for code reviews
Branches
Branches let you work on different features or experiments without affecting your main codebase.Key Branch Concepts
Default Branch
Default Branch
Every project has a default branch (usually called
main). This is the primary branch that represents your production-ready code.Feature Branches
Feature Branches
Create branches to work on new features or bug fixes. When ready, merge them back into the default branch.
Protected Branches
Protected Branches
Mark important branches as protected to prevent accidental deletion or unauthorized changes.
Branch Workflow
- Create a branch from
main - Make commits on your branch
- Compare your branch with
main - Merge when ready
Collaborators
Collaborators are team members who have access to your project. You invite them via email, and they can accept the invitation to join.Permission Levels
| Permission | Can View | Can Pull | Can Push |
|---|---|---|---|
| Read Only | Yes | Yes | No |
| Read & Write | Yes | Yes | Yes |
| Owner | Yes | Yes | Yes + Manage |
Only project owners can invite new collaborators, change permissions, or delete the project.
Files & File Versions
VibeHub tracks every version of every file in your project. You can:- Browse the current state of files on any branch
- View the file tree structure
- See syntax-highlighted code
- Compare different versions
File States
| State | Meaning |
|---|---|
| Added | New file introduced in a commit |
| Modified | Existing file was changed |
| Deleted | File was removed |
Integrations
VibeHub connects with other tools to enhance your workflow:GitHub
Import repositories from GitHub, bringing in your full commit history.Netlify & Vercel
Deploy your projects directly from VibeHub with one-click deployment integration.Glossary
| Term | Definition |
|---|---|
| Commit | A snapshot of your project at a point in time |
| Branch | A parallel line of development |
| Merge | Combining changes from one branch into another |
| Fast-forward | A merge where the target branch simply moves forward |
| Head | The latest commit on a branch |
| Diff | The differences between two versions of a file |
| Clone | Creating a local copy of a project |
| Push | Sending local changes to VibeHub |
| Pull | Getting changes from VibeHub to your local machine |