1
2
3
4
5
Docs › Workflow › Push to Production
Step 5 of 5

Push to Production

Zero-downtime deployments with instant rollbacks, automated previews, and built-in safety checks. Ship with confidence.

~/my-project $
git push origin main
Enumerating objects: 42, done.
Counting objects: 100% (42/42), done.
Compressing objects: 100% (18/18), done.
Writing objects: 100% (25/25), 14.2 KiB | 4.73 MiB/s, done.
✓ Deployment queued → us-east-1, eu-west-1, ap-southeast-1
✓ Health checks passed (200 OK)
✓ Live at: https://app.git.dev/my-project
git deploy status

⚡ Instant Rollbacks

Something broke? Revert to any previous commit in under 2 seconds with git deploy revert. Zero downtime, zero data loss.

🌐 Multi-Region Sync

Automatically propagate updates across all edge regions. Traffic shifts smoothly with DNS-based rolling updates.

🔍 Pre-Deploy Checks

Automated linting, type-checking, and security scans run before anything touches production. Fail fast, ship safely.

🛡️ Approval Gates

Require manual approval for production pushes. Integrate with Slack, PagerDuty, or your existing approval workflows.

Configuration

Control your production pipeline with a simple YAML config in .git/deploy.yml:

# .git/deploy.yml
production:
  regions: [us-east-1, eu-west-1, ap-southeast-1]
  rollback_on_error: true
  canary:
    enabled: true
    traffic_split: 5%
    duration: 5m
  notifications:
    slack: #deployments
    on_failure: true

Production Safety Net

✓

Health Check Validation

Automated HTTP/TCP checks before traffic switches to new instances.

✓

Canary Releases

Gradually roll out to a subset of users before full production deployment.

✓

Immutable Artifacts

Every deployment is versioned and traceable. No mutable production states.

✓

Automated Backups

Database snapshots created before each production push. Restore in one command.

Ready to ship?

Your repository is configured. Production is waiting.

Read API Reference