fix(setup): clarify settings-scope comment in runEnableOnConfiguredRepo

3224beb→main·

suhaanthayyil·4d ago·1 file·+5 added/-4

Changes

1. cmd/entire/cli
   • Msetup.go+5/-4

1118 unmodified lines

1119
1120
1121
1122
1123
1124
1122
1123
1124
1125
1126
1126
1127
1128
1129
1130

1118 unmodified lines

printEnabledStatus(ctx, w)
    return nil
}
// Enable in the same file the setup flow just wrote to. Without this, a plain
// `entire enable` (no --project/--local) resolves the strategy write to the
// existing project settings.json but wrote the enabled flag to
// Enable in the same settings target scope resolved by settingsTargetFile,
// which is also what strategy/checkpoint-backend updates above use. Without
// this, a plain `entire enable` (no --project/--local) resolved the strategy
// write to the existing project settings.json but wrote the enabled flag to
// settings.local.json, leaving the project file the user disabled still
// enabled=false (#1140). settingsTargetFile picks the correct scope.
// enabled=false (#1140).
targetFile, _ := settingsTargetFile(ctx, opts.UseLocalSettings, opts.UseProjectSettings)
return runEnable(ctx, w, targetFile == settings.EntireSettingsFile)
}

Mcmd/entire/cli/setup.go+5/-4