chore: disable db writes

[adityachoudhari26]

Summary by CodeRabbit

• Refactor
  • Switched changeset handling to an in-process no-op implementation within the workspace engine. No user-facing impact.
• Chores
  • Removed redundant database-backed dependency from the workspace component to reduce external coupling. No functional changes expected.

[coderabbitai]

Walkthrough

The workspace initialization now wires a no-op in-process changeset consumer (changeset.NewNoopChangesetConsumer()) instead of the DB-backed consumer. The db import was removed. Test constructor remains unchanged. No exported/public signatures were modified.

Changes

Cohort / File(s)	Summary
Workspace changeset consumer wiring apps/workspace-engine/pkg/workspace/workspace.go	Replaced db.NewChangesetConsumer() with changeset.NewNoopChangesetConsumer(), removed db import, no signature changes; NewTestWorkspace() remains using no-op consumer.

Sequence Diagram(s)

sequenceDiagram
    autonumber
    participant App as App
    participant WS as Workspace(New)
    participant CS as ChangesetConsumer
    participant DB as DB (previous)
    note over App,WS: Workspace initialization

    App->>WS: New()
    alt Previous (DB-backed)
        WS->>DB: db.NewChangesetConsumer()
        DB-->>WS: DB-backed consumer
        WS->>CS: Wire consumer (DB-backed)
    else Current (No-op)
        WS->>CS: changeset.NewNoopChangesetConsumer()
        CS-->>WS: No-op consumer
    end
    WS-->>App: Workspace instance
    note over WS: No DB dependency in current flow

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore: init changeset consumer interface #678 — Introduces and/or switches to changeset.NewNoopChangesetConsumer(), directly related to the wiring change here.

Poem

I twitch my ears at changes small,
Snip the DB, no calls at all—
A no-op hop through workspace lanes,
Quiet queues, unburdened chains.
Thump goes the log, serene and neat,
Carrot-commits now light on feet. 🥕🐇

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title “chore: disable db writes” concisely captures the primary change of replacing the database-backed changeset consumer with a no-op implementation to stop any writes, making it clear and directly relevant to the modifications introduced in the PR.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch disable-db-writes

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 0e5e317 and 2889a03.

📒 Files selected for processing (1)

• apps/workspace-engine/pkg/workspace/workspace.go (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

apps/workspace-engine/**/*.go

📄 CodeRabbit inference engine (apps/workspace-engine/CLAUDE.md)

apps/workspace-engine/**/*.go: Do not add extraneous inline comments that state the obvious
Do not add comments that simply restate what the code does
Do not add comments for standard Go patterns (e.g., noting WaitGroup or semaphore usage)
Write comments that explain why, document complex logic/algorithms, provide non-obvious context, include TODO/FIXME, and document exported functions/types/methods

Files:

• apps/workspace-engine/pkg/workspace/workspace.go

🧬 Code graph analysis (1)

apps/workspace-engine/pkg/workspace/workspace.go (1)

apps/workspace-engine/pkg/changeset/changeset_consumer.go (1)

• NewNoopChangesetConsumer (15-17)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Typecheck
• GitHub Check: Lint
• GitHub Check: build (linux/amd64)

🔇 Additional comments (1)

apps/workspace-engine/pkg/workspace/workspace.go (1)

17-17: No-op changeset consumer is safe. FlushChangeset on the no-op implementation always returns nil, so downstream error handling is unaffected and aligns with the PR’s intent.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}