GitHub
Mirror your generated app to a GitHub repo. Auto-commit on every change, branch per chat, optional pull-request flow. Useful when you want to layer your own CI, code review, or hand off to a development team.
#Two modes: auto-sync vs manual
| Field | Type | Description |
|---|---|---|
| Auto-sync | committed on change | Every file write commits to a chat-scoped branch within ~2s. No PRs by default. Best for solo work or when you trust the assistant. |
| Manual | commit on demand | You explicitly click "Push to GitHub" from the workbench. Good for review-before-merge workflows. |
Pick the mode at workspace setup. You can switch later from /settings/github.
#First-time setup
Connect your GitHub account
Go to /settings/github and click Connect. You'll be redirected to GitHub to authorize the PromptFloe OAuth app. We request repo scope so we can create repos and push commits.
Choose: new repo or existing
For each chat, you choose at first deploy:
- New repo — we create a private repo named after your chat.
- Existing repo — we push to a branch you specify.
Pick a branch strategy
By default each chat gets its own branch named promptfloe/<chat-id>. You can change this in the chat's settings to push directly to main or any other branch.
#Commit messages
Auto-sync commits use a structured format so your git history stays useful:
- build: initial generation from a prompt — title is a one-liner summary of the prompt.
- chore: follow-up edits to existing files.
- augment: changes from running an augmenter (e.g.
augment(seo): meta tags + sitemap). - skill: changes from a custom augmenter skill.
#Pull requests
For chat-scoped branches, you can promote any chat to a PR:
Click 'Open PR' from the workbench header
The PR is opened from the chat's branch into your repo's default branch. Title and body are auto-populated from the chat's session: prompt, files changed, augmenters applied.
Iterate and re-push
Subsequent edits in chat continue to push to the same branch and the PR auto-updates. Your reviewers see new commits as you iterate.
Merge from GitHub
PromptFloe doesn't merge for you. Use GitHub's merge UI as usual.
#When auto-sync hits a conflict
If someone else has pushed to the same branch (or you've edited locally outside PromptFloe), the next auto-sync push fails. The GitHub indicator turns red and a banner appears in the chat header.
You can resolve in three ways:
- Pull-and-rebase — let PromptFloe pull the remote, rebase your local changes, push again. Works for non-overlapping changes.
- Force-push — overwrite the remote with your local. Destructive; PromptFloe asks for explicit confirmation.
- Branch off — start a fresh branch from the current state and abandon the conflict.
#CI tips
Generated apps work with most CI providers without changes. A few things to know:
- Build command is
npm run build(orpnpm build); output isdist/. - Node 18+ is required for Vite-based templates.
.env.examplefiles are committed;.envfiles are gitignored by default.