Add branch analysis tool for identifying outdated branches

[Copilot]

Repository has 260 branches with no systematic way to identify which should be closed. Implemented automated analysis tool to categorize branches by age and merge status.

Implementation

• Analysis script (scripts/analyze-branches.js)

  • Fetches all remote branches
  • Categorizes into 5 priority groups: merged, stale (90+ days), outdated (60+ days), work-in-progress (30-90 days), recent (< 30 days)
  • Calculates days since last commit and divergence from main
  • Generates markdown report with deletion instructions

• npm command: npm run branches:analyze

• Documentation

  • BRANCH_MANAGEMENT.md - Usage guide, deletion guidelines, maintenance checklist
  • BRANCH_ANALYSIS_REPORT.md - Auto-generated report (current: 21 stale, 155 WIP, 83 recent)
  • BRANCH_ANALYSIS_IMPLEMENTATION.md - Technical overview

• README updates - Added useful scripts section and maintenance tool reference

Usage

$ npm run branches:analyze

Quick Summary:
  - Merged (can delete): 0
  - Stale (90+ days): 21
  - Outdated (60+ days): 0
  - Work in progress: 155
  - Recent: 83

See BRANCH_ANALYSIS_REPORT.md for detailed information.

Report includes branch name, last commit date, age, commits behind main, and subject line for each branch.

Original prompt

I don't know which branches should be closed out as out of date or not

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[netlify]

❌ Deploy Preview for sprightly-genie-998c07 failed. Why did it fail? →

Name	Link
🔨 Latest commit	5a24d6f
🔍 Latest deploy log	https://app.netlify.com/projects/sprightly-genie-998c07/deploys/690bc84d98a87300080b02e7

[DHCross]

Closing draft PR - branch analysis utility can be recreated if needed. The report generated is useful for reference but the PR itself is stale.