Skip to main content
Make your own GitHub repository the app’s source, so a push to its branch deploys dev. An app floo hosts moves there with every branch and tag.
Requires floo CLI v2026.11.09 or later (floo update).

What it does

The app’s URLs, env vars and databases stay as they are. A move needs an empty repository: create one first with gh repo create owner/repo --private. floo moves the history only into an empty repository, so nothing already there is overwritten. If a move stops partway, run the same command again: it pushes whatever is missing and finishes. The floo GitHub App must be able to read owner/repo. If it can’t, floo connect stops before anything moves and prints the link that fixes it. See GitHub access.

Flags

Examples

An app with a prod release keeps serving it. Its next release is a GitHub release on owner/repo.

API

floo connect pushes the history, then calls PUT /v1/apps/{app_id}/source with {"kind": "github", "repo": "owner/name"}. For an app floo hosts, the call refuses with HOSTED_HISTORY_NOT_PUSHED until every branch and tag of the hosted repository is in the new one.