Connector
How the GitHub connector works
The connector is intentionally operational, not administrative.
Create from the active project
The connector creates and seeds a repository from the project you already have open in Flutty.
Choose the account and repo details inside the workspace
Repository name, description, and visibility are set in the connector flow instead of a separate admin page.
Stay attached to the same project context
Sync actions belong to the project header, so you do not have to leave the workspace to keep source control aligned.
States
Follow the connector state that is shown
The connector changes its action set based on the current sync situation.
Connected
Local and remote are aligned closely enough that no special recovery action is required.
Syncing
Flutty is still applying or pushing connector work. Wait for that operation to finish before forcing more actions.
Remote update available
The remote changed and Flutty surfaces a refresh/apply path rather than assuming the local workspace should win automatically.
Conflict
Local and remote need an explicit conflict-resolution decision.
Error
The connector could not finish its last operation and may need a retry, refresh, or manual review.
Timing
When to connect GitHub
The best time to connect is once the workspace direction is already stable enough to preserve.
After the first working project direction is visible in preview
Before you need a remote checkpoint for collaboration or deployment
While the current workspace still clearly represents the source of truth
Practice
Use GitHub after the project direction is real
GitHub works best when you treat it as a durability and collaboration layer, not as the first step of creation.
Connect once the current project direction is worth preserving.
Let the workspace show you the next sync action instead of guessing whether to pull, push, or resolve.
Use the connector to keep the repo aligned with the same project you are previewing and iterating on.