Make Bridge Overview
Make Bridge mode syncs Figma Make's auto-created repositories to your own target repositories, overcoming Make's native limitations.
What Is Make Bridge?
When you use Figma Make to generate code from your designs, Figma automatically creates a GitHub repository. However, Make has limitations:
- Only pushes to auto-created repos (you can't choose the target)
- One-way sync only (no pulling back)
- Limited branch support
Make Bridge solves this by acting as a relay between Make's repo and your target repo.
┌────────────┐ ┌────────────┐ ┌────────────┐ ┌────────────┐
│ Figma │────►│ Make Repo │────►│ GitFig │────►│Target Repo │
│ Make │ │ (auto-gen) │ │ Server │ │ (your repo)│
└────────────┘ └────────────┘ └────────────┘ └────────────┘
│ │
└───── Webhook ─────┘
Key Features
| Feature | Description |
|---|---|
| Auto-sync | Webhook triggers sync when Make pushes |
| Target flexibility | Push to any repo you choose |
| Multiple strategies | Direct push, PR, or auto-merge |
| Reverse sync | Pull changes from target back to Make |
| Conflict detection | Warns when repos have diverged |
| File patterns | Include/exclude files from sync |
| GitHub Pages | Deploy directly from target repo |
When to Use Make Bridge
Good for:
- Deploying Make-generated code to your own repos
- CI/CD pipelines triggered by Make changes
- GitHub Pages deployments
- Teams needing PR-based reviews of Make output
Not needed for:
- Design token management (use Design Sync instead)
- Projects not using Figma Make
Sync Strategies
| Strategy | Behavior | Best For |
|---|---|---|
| Pull Request | Creates PR for each sync | Team review, protected branches |
| Direct Push | Pushes directly to target branch | Fast iteration, personal projects |
| Auto-Merge | Creates PR and auto-merges | CI validation, automated workflows |