Conversation
…ise-dev#2234) - Add DELETE /api/workspace/repos/{alias} endpoint to remove entries from .repowise-workspace.yaml - Reload workspace_config and clean up live in-memory server state without requiring a restart - Support synthetic ws: prefixed IDs in DELETE /api/repos/{repo_id} - Add removeWorkspaceRepo client function in @repowise-dev/api-client - Render RemoveWorkspaceRepoButton in web UI for missing_dir repos - Add comprehensive server unit tests in test_workspace_remove_repo.py
rishu685
force-pushed
the
fix/2234-workspace-remove-missing-dir-repo
branch
from
September 15, 2026 18:22
7c301dd to
4b3fb25
Compare
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.
Summary
Closes #2234
When a workspace member directory is removed or renamed on disk:
status: "missing_dir"and IDws:<alias>.missing_dirrows.DELETE /api/repos/ws:<alias>returned a 404 database error.repowise workspace remove <alias>) was not reflected in runningrepowise serveinstances because in-memoryworkspace_configwas only loaded at startup.Changes Made
Server Endpoints & Live State Sync:
DELETE /api/workspace/repos/{alias}inrouters/workspace.pyto drop the entry from.repowise-workspace.yamland save the file to disk.request.app.state.workspace_configand clean upworkspace_sessions,workspace_fts,workspace_path_to_repo_id, andworkspace_vector_storescaches so the running server immediately reflects the removal without requiring a restart.ws:<alias>ID handling inDELETE /api/repos/{repo_id}(routers/repos.py) to delegate cleanly to workspace configuration removal.WorkspaceRepoRemovedResponseschema.API Client:
removeWorkspaceRepo(alias)topackages/api-client/src/workspace.tsand exportedWorkspaceRepoRemovedResponseinterface.Web UI:
RemoveWorkspaceRepoButtoncomponent inpackages/web/src/app/workspace/sync-buttons.tsx.actionsForinpackages/web/src/app/workspace/page.tsxto display the "Remove" button whenrepo.status === "missing_dir".Unit Tests:
tests/unit/server/test_workspace_remove_repo.pycovering:.repowise-workspace.yamlDELETE /api/repos/ws:<alias>deletionVerification
pytest tests/unit/server/test_workspace_router.py tests/unit/server/test_workspace_remove_repo.py tests/unit/server/test_workspace_sidebar.py