memory: record repository workspace layout
This commit is contained in:
21
shared/long-term/decisions/repository-workspace-layout.md
Normal file
21
shared/long-term/decisions/repository-workspace-layout.md
Normal file
@@ -0,0 +1,21 @@
|
||||
# Repository workspace layout
|
||||
|
||||
## Decision
|
||||
|
||||
Code repositories cloned from Gitea or GitHub should live under `~/project`, not under `~/openclawd/vaults`.
|
||||
|
||||
Recommended base path:
|
||||
- `~/project/workspace/gitea/...`
|
||||
- `~/project/workspace/github/...`
|
||||
|
||||
## Rationale
|
||||
|
||||
- Keep `~/openclawd/vaults` clean for OpenClaw runtime, memory, skills, and configuration
|
||||
- Avoid mixing assistant-memory files with business/source repositories
|
||||
- Reduce context pollution and accidental edits in the memory/runtime workspace
|
||||
- Give ACP/opencode jobs a predictable code workspace
|
||||
|
||||
## Rule of thumb
|
||||
|
||||
- `~/openclawd/vaults` → OpenClaw runtime/config/memory only
|
||||
- `~/project/workspace/...` → cloned code repositories and active development work
|
||||
Reference in New Issue
Block a user