Summary
Projects in .github/projects/active/ must be manually moved to archived/ when complete. This is error-prone and creates inconsistency in project metadata.
Problem
- No automation to detect and archive completed projects
- Manual process is ad-hoc and unmaintained
- Risk: completed project metadata lost or inconsistently tracked
- No archival summary or historical record
Solution
Create new project-archival.yml workflow that:
- Triggers on-demand (workflow_dispatch) or on schedule (weekly)
- Scans active projects for completion markers:
- Project status: completed
- All associated issues: closed
- All associated PRs: merged or closed
- Moves completed project to
.github/projects/archived/{YYYY-MM-DD}-{project-name}/
- Creates archival summary including:
- Completion date & duration
- Final metrics (issues opened/closed, PRs merged)
- Project outcomes
- Commits archival record with clear git history
Implementation Details
- Effort: 3–4 hours
- Complexity: Medium
- Risk: Low (with dry-run mode and audit trail)
- Related: Project metadata structure (
.github/projects/)
- Dependencies: Project schema validation, GitHub API integration
Acceptance Criteria
Reference
See workflow standards audit: .github/reports/audits/workflow-standards-audit-2026-05-31.md
Summary
Projects in
.github/projects/active/must be manually moved toarchived/when complete. This is error-prone and creates inconsistency in project metadata.Problem
Solution
Create new
project-archival.ymlworkflow that:.github/projects/archived/{YYYY-MM-DD}-{project-name}/Implementation Details
.github/projects/)Acceptance Criteria
Reference
See workflow standards audit:
.github/reports/audits/workflow-standards-audit-2026-05-31.md