Repository navigation
feat: Warn at startup when the workspaces folder is not available - #747
Merged
Merged
Conversation
…older is missing A workspaces folder on a drive that is not attached (a Dev Drive that did not mount) made every cloned project fail to open and every workspace vanish from the sidebar, which looked like data loss. The app:start migrations hook now checks that the folder in use can be read and, when it cannot, shows a dialog naming it with Retry, Continue without it, and Quit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
paths.workspaces) on a drive that is not attached — e.g. a Windows Dev Drive that did not mount — made every managed clone fail to open (Cannot use simple-git on a directory that does not exist) and every workspace in it disappear from the sidebar, which read as data loss (seen in a bug report from a Windows install)migrationshook of the workspaces-root module now checks that a non-default root can be read before anything opens; when it cannot, the starting screen shows a modal naming the folder, with Retry, Continue without it (today's behaviour, root unchanged) and Quit🤖 Generated with Claude Code