38ce7e4bc5
## Summary Added tools and process for managing PR backlog in timmy-config. ## Problem timmy-config has 31+ open PRs, the highest in the organization. This creates confusion, slows down development, and increases merge conflicts. ## Solution Created automated tools and process for PR backlog management: ### 1. PR Backlog Analyzer (`scripts/pr-backlog-analyzer.py`) - Fetches all open PRs from timmy-config - Analyzes age, review status, labels - Generates markdown report - Categorizes PRs: stale, needs review, approved, changes requested ### 2. GitHub Actions Workflow (`.github/workflows/pr-backlog-management.yml`) - Runs weekly on Monday at 10 AM UTC - Analyzes PR backlog - Creates issue if backlog is high (>10 stale PRs) - Uploads report as artifact ### 3. Documentation (`docs/pr-backlog-process.md`) - Weekly analysis process - Review stale PRs procedure - Merge approved PRs workflow - Review pending PRs SLA - Close duplicate PRs process - Metrics to track - Escalation procedures ## Usage ### Run Analyzer ```bash python scripts/pr-backlog-analyzer.py ``` ### View Report ```bash cat reports/pr-backlog-$(date +%Y%m%d).md ``` ## Metrics - **Current**: 32 open PRs in timmy-config - **Target**: <20 open PRs - **SLA**: Review within 48 hours, merge within 7 days Issue: #1470
Scripts
cleanup-duplicate-prs.sh
Automated detection and cleanup of duplicate open PRs.
Purpose
This script identifies PRs that are duplicates (same issue number or very similar titles) and closes the older ones. It's designed to help maintain a clean PR board and prevent confusion from duplicate work.
Features
- Issue-based grouping: Groups PRs by issue number extracted from titles
- Date-based selection: Keeps the newest PR, closes older duplicates
- Dry-run mode: Shows what would be done without making changes
- Stale PR detection: Identifies PRs older than 30 days with no activity
- Explanatory comments: Adds comments when closing PRs to explain why
Usage
# Dry run (default) - shows what would be done
./scripts/cleanup-duplicate-prs.sh
# Actually close duplicates
./scripts/cleanup-duplicate-prs.sh --close
# Set environment variables
export GITEA_TOKEN="your_token_here"
export REPO="Timmy_Foundation/the-nexus"
export GITEA_URL="https://forge.alexanderwhitestone.com"
Configuration
The script uses the following environment variables:
| Variable | Default | Description |
|---|---|---|
GITEA_TOKEN |
(required) | Gitea API token with repo access |
GITEA_URL |
https://forge.alexanderwhitestone.com |
Gitea instance URL |
REPO |
Timmy_Foundation/the-nexus |
Repository in owner/repo format |
DRY_RUN |
true |
Set to false to actually close PRs |
How It Works
- Fetch open PRs: Gets all open PRs from the repository
- Extract issue numbers: Parses issue numbers from PR titles (e.g.,
#123) - Group by issue: Groups PRs that address the same issue
- Identify duplicates: Finds issues with multiple open PRs
- Select newest: For each duplicate group, keeps the newest PR
- Close older PRs: Closes older duplicates with explanatory comments
- Check for stale PRs: Identifies PRs older than 30 days
Example Output
[2026-04-14T00:57:05Z] Checking open PRs for Timmy_Foundation/the-nexus (dry_run: true)
[2026-04-14T00:57:17Z] Found 14 open PRs
[2026-04-14T00:57:17Z] Issue #1338 has 2 open PRs
[2026-04-14T00:57:17Z] Keeping PR #1392 (newest)
[2026-04-14T00:57:17Z] DRY RUN: Would close PR #1388
[2026-04-14T00:57:17Z] Issue #1354 has 2 open PRs
[2026-04-14T00:57:17Z] Keeping PR #1391 (newest)
[2026-04-14T00:57:17Z] DRY RUN: Would close PR #1384
[2026-04-14T00:57:17Z] Cleanup complete:
[2026-04-14T00:57:17Z] Duplicate issue groups found: 4
[2026-04-14T00:57:17Z] PRs closed: 0
[2026-04-14T00:57:17Z] Dry run: true
Safety Features
- Dry-run by default: Won't close PRs unless explicitly told to
- Explanatory comments: Adds comments before closing to explain why
- Newest PR preserved: Always keeps the most recent PR for each issue
- No force deletion: Only closes PRs, doesn't delete branches
Integration
This script can be integrated into CI/CD pipelines or run manually as part of regular maintenance. It's designed to be run weekly to keep the PR board clean.
Related Issues
- Issue #1128: Forge Cleanup — PRs Closed, Milestones Deduplicated, Policy Issues Filed
- Issue #1127: Evening triage pass (predecessor to #1128)