How .git Works

From local commit to global deployment in seconds. Here’s exactly how the pipeline processes your code, validates changes, and ships them to production.

Step 01

Initialize & Connect

Link your existing repository or create a new one. .git auto-detects your framework, package manager, and dependency structure.

                        
                        # Initialize a new .git project
                        $ git init my-app && cd my-app

                        $ git connect github:username/repo

                        ✓ Repository linked. Framework detected: Next.js 14

Step 02

Configure Pipeline Rules

Define build commands, test suites, and deployment targets using YAML or our visual editor. Zero-config defaults are applied automatically.

                        
                        # .git.yaml
                        build: npm run build

                        test: npm test -- --coverage

                        deploy: edge: global

                        branches: main → production

Step 03

Commit & Push

Push to any branch. .git intercepts the webhook, spins up an isolated build environment, and runs your pipeline automatically.

                        
                        $ git add . && git commit -m "feat: add auth flow"

                        $ git push origin main

                        → Pipeline triggered (#4821)

Step 04

Preview & Validate

Every branch gets a live preview URL. Run automated tests, Lighthouse audits, and manual reviews before merging.

                        
                        ✓ Build succeeded in 12.4s

                        ✓ Tests passed (142/142)

                        🔗 Preview: https://feat-auth-4821.git.dev

Step 05

Deploy to Production

Merge to main. .git rolls out the update globally with zero downtime. Automatic rollback on error detection.

                        
                        $ git deploy --prod --strategy=canary

                        ✓ Live at: https://my-app.git.dev

                        ✓ Edge cache refreshed. Rollback ready.

The Automated Pipeline

Behind the scenes, every commit flows through a secure, parallelized execution engine.

📥

Webhook

Git push detected

→

🛠️

Build

Isolated env

→

🧪

Test

CI + coverage

→

👁️

Preview

Branch URL

→

🚀

Deploy

Edge / Cloud

Declarative Configuration

Define your entire workflow in a single .git.yaml file. Version it alongside your code, share it across teams, and enforce consistency.

Framework auto-detection (React, Next.js, Svelte, Go, Python, etc.)
Branch-based routing & environment isolation
Custom build commands & Docker support
Role-based deployment permissions

# .git.yaml project: my-app build: command: npm run build output: ./out cache: true test: command: npm test coverage: true deploy: target: edge-global strategy: blue-green rollback: auto

Common Questions

Everything you need to know about the workflow.

How fast are deployments?

Average build times are 8-15 seconds for standard web apps. Production deploys typically complete in 2-4 seconds thanks to our edge caching and parallelized rollout system.

Can I use my own CI/CD tools?

Yes. .git integrates seamlessly with GitHub Actions, GitLab CI, and Jenkins. You can also run .git as the deployment target while keeping your existing test suites.

What happens if a deploy fails?

.git automatically rolls back to the last known stable version. You'll receive an instant alert, a diff report, and a one-click retry option. Zero traffic impact.

Is monorepo support available?

Absolutely. .git natively understands Turborepo, Nx, and Lerna setups. We only rebuild and deploy affected packages, saving compute and time.

Ready to automate your workflow?

Connect your repo and deploy your first app in under 3 minutes.

Start Building Free →