Prune PR branches
Open
enhancement
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue provides no description, files, tests, or entry points. Start by determining which pull-request branches should be pruned and where repository automation or branch-management behavior belongs; done means the intended branches are removed safely without affecting active work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100