Stop hardcoding port

README.md

@@ -75,8 +75,6 @@ Supported variable names:
 - `GITEA_URL` or `GITEA_BASE_URL`
 - `GITEA_OWNER`
 - `GITEA_TOKEN` or `GITEA_ACCESS_TOKEN`
-- `GITEA_SSH_USER` (defaults to `git`)
-- `GITEA_SSH_PORT` (only needed for a non-default SSH port)
 
 Token handling behavior:
 
@@ -84,10 +82,11 @@ Token handling behavior:
 - Otherwise token is requested in the TUI
 - Token is not persisted by `git-tui`
 
-When connecting an existing Gitea repository by `owner/name`, choose SSH to
-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.
+When connecting an existing Gitea repository, paste the complete clone URL or
+provide `owner/name` and ask the Gitea API to return its exact clone endpoints.
+The app does not derive an SSH endpoint from the web URL because the SSH user,
+host, and port can differ. Private API lookups require a token; pasting the
+clone URL does not.
 
 Creating a Gitea repository still uses an API token, because Git/SSH cannot
 create repositories. The Git remote transport is selected separately; choosing
@@ -99,6 +98,11 @@ 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.
 
+Network Git commands temporarily leave the curses screen and use the real
+terminal. SSH passphrase prompts, HTTPS username/token prompts, and interactive
+credential helpers therefore behave as they do for Git commands run directly
+from the shell.
+
 ## Keybindings
 
 - Main menu: