Fix stale git-refs skip reason in alternates test

c41e19d·

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

The skip message said the git-refs store force-pushes per-checkpoint refs, but git-refs switched to non-force fast-forward pushes with fetch+replay recovery. The test is still git-branch-specific (it exercises the v1 branch's rebase-sync path over an object alternate, which git-refs has no equivalent of); only the reason text needed correcting.

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

Sessions

84e64cc670b3View transcript

Changes

1

• e2e/tests

• Malternates_test.go+1/-1

24 unmodified lines

25
26
27
28
28
29
30
31

24 unmodified lines

// checkpoint commits, even though git itself resolves them.
func TestAlternates_RelativeObjectAlternate_CheckpointSync(t *testing.T) {
    if testutil.UsingGitRefs() {
        t.Skip("git-branch-specific: exercises the v1 checkpoint branch's non-fast-forward push/rebase sync over an object alternate; the git-refs store force-pushes independent per-checkpoint refs with no such rebase path")
        t.Skip("git-branch-specific: exercises the v1 checkpoint branch's non-fast-forward push/rebase sync over an object alternate; the git-refs store writes independent per-checkpoint refs (fast-forward push with fetch+replay recovery) and has no such v1-branch rebase path")
    }
    // Siblings under one parent so the relative alternate path is short and
    // mirrors a real shared-clone layout.

Me2e/tests/alternates_test.go+1/-1