Fix Git Flow

README.md

@@ -47,13 +47,19 @@ gtui
 If the directory is not a Git repository, `git-tui` offers:
 
 - Initialize repository only
-- Initialize and publish to a new remote repository
+- Initialize, create a Gitea remote, and sync local commits to it
+- Initialize, connect an existing Gitea remote, and synchronize both sides
 
 If the directory is already a Git repository but has no remote configured, `git-tui` offers:
 
-- Connect to an existing remote repository
+- Create a Gitea remote and sync
+- Connect an existing Gitea remote and sync
 - Continue without remote
 
+When a remote is configured, the normal operations menu includes an action to
+disconnect it. Disconnecting removes only the local remote configuration; it
+does not delete the Gitea repository.
+
 ## Gitea Setup
 
 For Gitea publish flow, you can provide values interactively in the TUI or pre-set environment variables:
@@ -83,6 +89,16 @@ use an SSH key already configured on the machine, or HTTPS to use a configured
 Git credential helper. You can also paste a complete clone URL to use it
 unchanged.
 
+Creating a Gitea repository still uses an API token, because Git/SSH cannot
+create repositories. The Git remote transport is selected separately; choosing
+SSH leaves the new `origin` configured with Gitea's SSH clone URL.
+
+Synchronization compares local and remote commit history. It fast-forwards or
+pushes automatically when one side is ahead. If the histories diverge, the UI
+offers to merge, replace local history after creating a backup branch, or
+force-push local history with `--force-with-lease`. Uncommitted changes must be
+committed or stashed first and are never silently discarded.
+
 ## Keybindings
 
 - Main menu: