Skip to main content

​
Usage

vibe push [options]

​
Description

Push your local commits to your VibeHub project in the cloud. This syncs your local changes with the remote repository, including any captured AI prompts.

​
Options

​
--force
boolean
Force push even if there are conflicts. Use with caution.
​
--dry-run
boolean
Preview what would be pushed without actually pushing.
​
--project-id
string
Specify a project ID to push to. Useful when working with multiple projects.
​
--branch
string
Specify which branch to push to (defaults to current branch).

​
Examples

​
Basic Push

vibe push
Pushes all new commits to the connected VibeHub project.

​
Preview Changes

vibe push --dry-run
Shows what would be pushed without actually pushing. Useful for verification.

​
Force Push

Force pushing will overwrite remote changes. Make sure you know what you’re doing.
vibe push --force

​
Push to Specific Project

vibe push --project-id 12345

​
What Gets Pushed

When you push, VibeHub receives:
ContentIncluded
Commit messageYes
Changed filesYes
File contentsYes
Author informationYes
TimestampYes
AI prompts (if captured)Yes

​
Prerequisites

Before pushing, ensure you have:
  1. Authenticated with vibe login
  2. Initialized your project with vibe init
  3. Connected to a VibeHub project with vibe set <project-url>

​
Push Workflow

​
Output

A successful push shows: 
Pushing to vibehub.co.in/username/project-name...
✓ 3 commits pushed
✓ 12 files synced
✓ 5 prompts captured
Push complete!

​
Error Handling

​
Not Connected

Error: No project connected. Run 'vibe set <project-url>' first.
Solution: Connect to a project with vibe set.

​
Not Authenticated

Error: Not logged in. Run 'vibe login' first.
Solution: Authenticate with vibe login.

​
Network Error

Error: Could not connect to VibeHub. Check your internet connection.
Solution: Check your internet connection and try again.

​
Conflicts

Error: Remote has changes. Pull first or use --force.
Solution: Either pull remote changes with vibe pull or force push with --force.

​
Best Practices

Push often to keep your remote in sync and avoid large uploads.
When unsure, use --dry-run to preview what will be pushed.
Force pushing can overwrite others’ work. Use only when necessary.
Run vibe status before pushing to see what will be synced.