Skip to main content
Branches keep work isolated until you are ready to merge it. Each Branch has its own code, content, and hosted Preview. Fimo keeps that Preview current in the background after you push code or change content, so opening a Branch shows its latest state. Fimo targets the Branch you have checked out in Git. If Git cannot name a Branch, such as at a detached commit, check out a Branch before running locally. CLI commands can target another Branch with --branch <name>.

​
The safe path to production

  1. Create a Branch for the change.
  2. Deploy that Branch to Preview.
  3. Review its code and content changes.
  4. Merge the Branch into main.
  5. Publish main to production.
Preview and production stay separate throughout this flow. Deploying a Branch does not make it public.

​
Work with Branches

Use fimo checkout -b instead of git checkout -b. The Fimo command creates both the Git branch and its isolated Fimo environment. A connected MCP client reads the same comparison without a checkout through fimo.branches.status and fimo.branches.diff. See Project MCP.

​
Group Branches into Environments

Every project has Preview and Production. Preview contains Branches that are not assigned to a custom Environment. Production represents the published site. If your plan includes custom Environments, you can group Branches by exact names or trailing wildcard patterns:
Deleting a custom Environment does not delete its Branches. They return to Preview.

​
What’s next

Preview vs production

Keep review links separate from the public site.

Launch checklist

Move from reviewed Preview to a verified launch.

Version history

Save and restore project states.