Skip to content

An option to disable git snapshots#1171

Closed
cvzakharchenko wants to merge 1 commit into
anomalyco:devfrom
cvzakharchenko:feature/disable-git-snapshot
Closed

An option to disable git snapshots#1171
cvzakharchenko wants to merge 1 commit into
anomalyco:devfrom
cvzakharchenko:feature/disable-git-snapshot

Conversation

@cvzakharchenko

Copy link
Copy Markdown
Contributor

Otherwise it takes an enormous amount of time on a large repo:

  INFO  2025-07-19T07:42:05 +0ms service=app name=tool.filetimes registering service
  INFO  2025-07-19T08:08:17 +1572073ms service=server duration=1589896 response
  INFO  2025-07-19T08:16:14 +476882ms service=snapshot added files
  INFO  2025-07-19T08:17:07 +53474ms service=session session=ses_7e3846879ffe1nGX38z2KH6uZ2 type=start-step part

@cvzakharchenko

Copy link
Copy Markdown
Contributor Author

I want to clarify, this log is on a git repo. So the logic that disables snapshots on non-git repos doesn't help.

bussard76 pushed a commit to bussard76/openwork that referenced this pull request May 12, 2026
* Isolate OpenCode dev state and clarify destructive reset

Route dev-mode OpenCode state into a dedicated openwork-dev-data home so local development never touches the default user path. Move the destructive reset to Debug and make it wipe only the current mode's OpenWork and OpenCode state with an explicit irreversible warning.

* Unify managed OpenCode state paths

Keep the supported desktop/orchestrator flow on a single OpenCode state root per mode instead of creating per-workspace directories. This makes dev and production resets target the right shared paths without changing the standard non-dev OpenCode data locations.

---------

Co-authored-by: src-opn <src-opn@users.noreply.github.com>
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.

2 participants