# Fix stale force-push wording in prePushCheckpointRefs doc

`c887107`→[main](/content/gh/entireio/cli/commits/main/index.html)·

Soph·2w ago·1 file·+3 added/-2 removed

The git-refs pre-push path was switched to fast-forward-only pushes with
fetch+replay recovery; the doc comment still said "batch force-pushes". Wording
only — no behavior change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

## Sessions

f758baeca44cView transcript

[?\\
Build Checkpoints Store Based on DesignClaude Code·Opus 4.8·1 step](/content/gh/entireio/cli/session/6852b33a-0d22-4364-aa6c-8de706ecc215#timeline-f758baeca44c/index.html)

## Changes

1

- cmd/entire/cli/strategy

- Mmanual_commit_push.go+3/-2

```go
129 unmodified lines

130
131
132
133
134
133
134
135
136
137
138

129 unmodified lines

\treturn nil
// prePushCheckpointRefs drains the per-checkpoint push queue and batch force-pushes
// the recorded refs (git-refs primary). Transient push failures are logged and
// prePushCheckpointRefs drains the per-checkpoint push queue and batch-pushes the
// recorded refs fast-forward-only (git-refs primary; never a force push — a
// diverged ref is recovered via fetch+replay). Transient push failures are logged and
// swallowed — like the v1 path, they must not block the user's git push — and the
// refs stay queued for the next pre-push. OPF is not applied (it is descoped for
// the git-refs store for now).
```

Mcmd/entire/cli/strategy/manual_commit_push.go+3/-2