Support

Integrations

Understand each Git sync state before acting

The connector surfaces different actions depending on whether Flutty, GitHub, or both sides changed. Read the state first, then choose the right move.

Integrations2 sections

States

What the main states mean

Each state is a signal about which side currently needs your attention.

Connected

GitHub is linked and ready for continued sync after successful runs.

GitHub ahead

Remote commits exist that are not represented in the current workspace yet.

Conflict

Both Flutty and GitHub changed since the last shared commit, so you need an explicit choice.

Error

The last sync failed and should be retried only after the underlying issue is understood.

Recovery

Handle conflicts deliberately

Conflict handling is safest when you choose the authority explicitly.

Check whether the workspace or the remote reflects the intended source of truth.

Pull GitHub only when the remote should replace the current workspace on purpose.

Retry failed syncs from the same project after the issue is understood.