Skip to content

Run initial sync after Cloud Sync connect#132

Open
bholmesdev wants to merge 1 commit into
mainfrom
codex/issue-39-enable-cloud-sync-local-workspace
Open

Run initial sync after Cloud Sync connect#132
bholmesdev wants to merge 1 commit into
mainfrom
codex/issue-39-enable-cloud-sync-local-workspace

Conversation

@bholmesdev

Copy link
Copy Markdown
Owner

Closes #39

Summary:

  • Run the existing sync engine immediately after hubble cloud create or hubble cloud connect writes the Cloud Sync linkage.
  • Update command help and changelog to reflect that create/connect now backfill local files/assets right away.

Checks:

  • pnpm --filter @hubble.md/cli... build
  • pnpm exec biome check packages/cli/src/index.ts CHANGELOG.md
  • pnpm check
  • pnpm build:desktop

E2E:

  • CLI help smoke: node packages/cli/dist/index.js cloud create --help && node packages/cli/dist/index.js cloud connect --help.
  • No desktop UI e2e needed; this is CLI Cloud Sync behavior.

Notes:

  • pnpm --filter @hubble.md/cli build alone still fails because workspace dependencies are not built in isolation; @hubble.md/cli... passes and matches the monorepo dependency build pattern.
  • Build logs include the existing apps/web Node 22.x engine warning under current Node v24.14.0.
  • No codex / codex-automation labels exist in this repo.

Co-Authored-By: Oz <oz-agent@warp.dev>
@vercel

vercel Bot commented Jul 3, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
hubble-md-web Ready Ready Preview, Comment Jul 3, 2026 11:38pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enable Cloud Sync on a local Workspace

1 participant