Developer
b26ed7c3e4
Working copies were stored as /data/working-copies/{repo_id}/{workspace_name}/,
so git clone was forced into a user-named directory. That meant the container
mount basename was the workspace name (e.g. main) instead of the repo name.
- Generate the workspace UUID before cloning and clone into
/data/working-copies/{workspace_id}/ so git creates {repo_name}/ naturally
- Set workspace.path to /data/working-copies/{workspace_id}/{repo_name}/
- Update _migrate_clone_into_workspace() to use the same layout
- _get_repository_mount_name() now prefers workspace.path basename and only
falls back to remote URL / repo.name for legacy repo-only instances
- Update unit tests to assert workspace path basename is used for mounts
Quality gates:
- pytest tests/unit: 219 passed
- ruff: clean on changed files
- mypy: clean on changed files
21 lines
599 B
Markdown
21 lines
599 B
Markdown
# openspec/changes/fix-pi-container-mount-permissions (index)
|
|
dir: openspec/changes/fix-pi-container-mount-permissions
|
|
|
|
## role
|
|
Documents a bug fix for container filesystem permission issues affecting Pi agent repository mounts and npm operations in containerized development environments.
|
|
## parent
|
|
index: openspec/changes/.pi-map.index.md
|
|
map: openspec/changes/.pi-map.md
|
|
## children
|
|
-
|
|
## files
|
|
- change.md
|
|
- tasks.md
|
|
## links
|
|
index: openspec/changes/fix-pi-container-mount-permissions/.pi-map.index.md
|
|
map: openspec/changes/fix-pi-container-mount-permissions/.pi-map.md
|
|
## workflows
|
|
-
|
|
## dirty
|
|
-
|