Problem Statement
No stale issue management workflow exists. Issues and PRs accumulate without review, creating noise and making it hard to track actionable items.
Evidence
- No stale workflow in
.github/workflows/
Impact
Issue tracker accumulates stale items. Maintainer overhead increases.
Proposed Solution
Create .github/workflows/stale.yml with actions/stale: mark issues/PRs as stale after 60 days of inactivity, close after 14 more days.
Technical Requirements
- Must exempt issues labeled 'pinned', 'security', or 'epic'
- Must label stale items with 'stale'
- Must comment before closing
Acceptance Criteria
- Workflow runs on schedule (daily)
- Issues/PRs without activity for 60 days are marked stale
- Stale items without activity for 14 more days are closed
- Exempt labels prevent auto-stale marking
File Inventory
.github/workflows/stale.yml (new)
Dependencies
None.
Testing Strategy
- Dry-run workflow on test repository
Security Considerations
Security issues must be exempt from auto-closing.
Definition of Done
Problem Statement
No stale issue management workflow exists. Issues and PRs accumulate without review, creating noise and making it hard to track actionable items.
Evidence
.github/workflows/Impact
Issue tracker accumulates stale items. Maintainer overhead increases.
Proposed Solution
Create
.github/workflows/stale.ymlwith actions/stale: mark issues/PRs as stale after 60 days of inactivity, close after 14 more days.Technical Requirements
Acceptance Criteria
File Inventory
.github/workflows/stale.yml(new)Dependencies
None.
Testing Strategy
Security Considerations
Security issues must be exempt from auto-closing.
Definition of Done