Fix stale force-push wording in prePushCheckpointRefs doc

8d1f57c·

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

Changes

1

• cmd/entire/cli/strategy

• Mmanual_commit_push.go+3/-2

121 unmodified lines

122
123
124
125
126
125
126
127
128
129
130

121 unmodified lines

return 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