alex/headquarter
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(project-map): regenerate .pi-map artifacts across the repo

Browse Source
This commit is contained in:
Developer
2026-06-17 11:31:24 +00:00
parent 0dd5f2317b
commit 93da9b42a2
683 changed files with 5075 additions and 4965 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/archive/2026-06-14-completed-specs-archive/git-repo/.pi-map.md
+7 -7
View File
@@ -1,16 +1,16 @@
# 2026-06-14-completed-specs-archive/git-repo
dir: 2026-06-14-completed-specs-archive/git-repo
# openspec/changes/archive/2026-06-14-completed-specs-archive/git-repo
dir: openspec/changes/archive/2026-06-14-completed-specs-archive/git-repo
index: 2026-06-14-completed-specs-archive/git-repo/.pi-map.index.md
index: openspec/changes/archive/2026-06-14-completed-specs-archive/git-repo/.pi-map.index.md
## role
Defines specifications for a bare git repository management service that bridges filesystem storage with database-backed metadata and SSH key integration.
Defines requirements for a git repository management system with bare repo lifecycle operations, SSH key integration, and duplicate prevention.
## files
- spec.md | Specifies requirements for managing bare git repositories on disk with database metadata, including creation, SSH key association, cloning, listing, deletion, and duplicate prevention. | dep: Database models (GitRepository, Project, User), Docker volume for repo storage
- spec.md | Defines requirements for a git repository management system that handles bare repository creation, SSH key association, cloning, listing, deletion, and duplicate prevention with on-disk storage and database metadata. | dep: GitRepository, Project, User, Docker volume, SSH key system, pytest, mypy, ruff, npm
## arch
Specification-driven domain design with clear separation between storage operations (create/clone/delete), metadata persistence, and access control (SSH keys), emphasizing idempotency and duplicate prevention constraints.
Specification-driven design using markdown-based requirements documentation with clear functional boundaries between storage layers (filesystem + database) and explicit constraint definitions.
## tags
spec, specifies, requirements, managing, bare, git, repositories, disk
repository, spec, defines, requirements, git, management, system, handles
## symbols
-
## workflows