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/2025-05-18-git-repo-management/.pi-map.md
+10 -10
View File
@@ -1,19 +1,19 @@
# 2025-05-18-git-repo-management
dir: 2025-05-18-git-repo-management
# openspec/changes/archive/2025-05-18-git-repo-management
dir: openspec/changes/archive/2025-05-18-git-repo-management
index: 2025-05-18-git-repo-management/.pi-map.index.md
index: openspec/changes/archive/2025-05-18-git-repo-management/.pi-map.index.md
## role
This package contains design and planning documents for implementing a git repository management feature that enables creating, listing, cloning, and deleting bare git repositories within projects.
Contains completed specification documents for implementing git repository management feature in an existing project/SSH-key platform.
## files
- .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
- design.md | Design document specifying a bare git repository management system for projects with create/list/clone/delete operations | dep: git, filesystem, database, API, Dockerfile
- proposal.md | Proposes a feature to add git repository creation, cloning, and management capabilities within existing projects | dep: project-management, git, backend API, frontend UI, disk storage
- tasks.md | Project task checklist tracking implementation of a Git repository management feature across backend API, frontend UI, and project integration with verification steps.
- .openspec.yaml | Defines an OpenAPI specification metadata file with schema type and creation date
- design.md | Design document for adding bare git repository management to a platform that already has projects and SSH keys | dep: git, subprocess, filesystem storage, database, API, frontend
- proposal.md | Proposes adding git repository management functionality to a platform that already has projects but lacks repository creation and management capabilities | dep: git, backend API, frontend UI, disk storage, project management system
- tasks.md | This is a completed task checklist for implementing a Git repository management feature with backend API, frontend UI, project integration, and verification steps. | dep: FastAPI, Pydantic, React, git, pytest, ruff, mypy, npm, docker-compose
## arch
Documentation-driven specification pattern using layered design docs (proposal → design → tasks → API spec) to formally define requirements before implementation, with clear separation between backend API, frontend UI, and project integration concerns.
Specification-driven development with layered documentation (proposal → design → tasks) plus OpenAPI metadata, following a structured change request process with clear separation of backend API, frontend UI, and integration concerns.
## tags
git, management, design, repository, project, creation, .openspec, projects
git, repository, management, design, creation, .openspec, adding, platform
## symbols
-
## workflows