Update README plan wording

1dbdf39→main·

Soph·3mo ago·1 file·+2 added/-2

Sessions

fb72ba1a2199View transcript

[?
Can you take a look at the go code (wasm) in /Users/soph/Work/entire/devenv/entire-io-worktree1 based a bit on that I wonder if something like this can be build:Codex·GPT-5.4·2 steps](/content/gh/entireio/git-sync/session/019d6d29-8cf7-7fe3-adc9-8c3e4d9d5603#timeline-fb72ba1a2199/index.html)

Changes

1

• MREADME.md+2/-2

150 unmodified lines

151
152
153
154
154
155
156
157
22 unmodified lines

180
181
182
183
183
184
185
186

150 unmodified lines

Dry run:

```bash
go run ./cmd/git-sync sync --dry-run --stats <source-url> <target-url>
go run ./cmd/git-sync plan --stats <source-url> <target-url>
```

## Auth
22 unmodified lines

- Branches are updated only when the target tip is an ancestor of the source tip, unless `--force` is set.
- Tags are immutable by default. Retargeting an existing tag requires `--force`.
- If `--prune` is set, managed target refs that are absent on source are deleted.
- If any ref would be blocked and `--dry-run` is not set, the command exits non-zero before pushing anything.
- `plan` never pushes. If `sync` finds blocked refs, it exits non-zero before pushing anything.
- `--stats` adds per-service request, byte, want, have, and command counters to the output.

## Why Push Stays V1

MREADME.md+2/-2