Skip to content

fix(cli): preserve sync skip flags#10

Merged
vincentkoc merged 1 commit into
mainfrom
codex/fix-sync-skip-flags-openclaw
May 18, 2026
Merged

fix(cli): preserve sync skip flags#10
vincentkoc merged 1 commit into
mainfrom
codex/fix-sync-skip-flags-openclaw

Conversation

@vincentkoc
Copy link
Copy Markdown
Member

Summary

  • Preserve explicit sync --no-transcripts and --no-panels opt-outs when config defaults enable transcripts or panels.
  • Add parser and desktop-cache regression coverage for the skip flags.
  • Add a concise changelog line for the user-visible CLI behavior fix.

Supersedes #2 with the OpenClaw module-path correction and fresh validation.

Verification

  • /Users/vincentkoc/GIT/_Perso/openclaw/.agents/skills/autoreview/scripts/autoreview --parallel-tests 'GOWORK=off go mod tidy && git diff --exit-code -- go.mod go.sum && GOWORK=off go vet ./... && GOWORK=off go test ./... && GOWORK=off go run golang.org/x/vuln/cmd/govulncheck@v1.3.0 ./...'
  • git diff --check HEAD~1..HEAD

Behavior addressed: sync --no-transcripts and --no-panels now override config defaults that would otherwise re-enable those archive sections.
Real environment tested: local maintainer worktree from current origin/main.
Exact steps or command run after this patch: autoreview helper with go mod tidy, go vet, go test ./..., and govulncheck.
Evidence after fix: parser test keeps skip flags; desktop-cache regression archives the note without transcript chunks.
Observed result after fix: all checks passed and autoreview reported no accepted/actionable findings.
What was not tested: live Granola API sync with real credentials.

@github-actions github-actions Bot added the fix label May 18, 2026
@vincentkoc vincentkoc merged commit 51f1a41 into main May 18, 2026
13 checks passed
@vincentkoc vincentkoc deleted the codex/fix-sync-skip-flags-openclaw branch May 18, 2026 06:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants