Skip to content

docs: repository-maintenance - Align branch cleanup runbooks #1245

Description

@ashleyshaw

Create comprehensive, permanent documentation for branch cleanup and repository maintenance procedures.

Deliverables

  • ✅ docs/BRANCH_CLEANUP.md (330 lines)

    • Quick start guide
    • How it works (4 subsections)
    • Command reference
    • Workflow integration
    • Troubleshooting (6 issues)
    • FAQ (11 entries)
  • ✅ docs/MAINTENANCE.md (330 lines)

    • Monthly maintenance calendar
    • 5 core procedures
    • Automated task registry
    • Health checks
    • Escalation guidelines

Related Files

  • docs/BRANCH_CLEANUP.md
  • docs/MAINTENANCE.md
  • BRANCHING_STRATEGY.md (updated)

Project Reference

Parent Epic: #1243
Project: projects/active/repository-maintenance-infrastructure/


Definition of Ready (DoR)

  • Problem statement and outcome defined
  • Acceptance criteria written (Given/When/Then)
  • Designs/specs/references attached (if relevant)
  • Dependencies mapped
  • Estimate added
  • Stakeholders/approvers listed
  • Milestone/iteration assigned (if applicable)

Definition of Done (DoD)

  • All acceptance criteria met
  • Tests added/updated; CI green
  • Accessibility: WCAG 2.2 AA compliance verified (semantic HTML, keyboard support, colour contrast)
  • Security: input validated, output escaped, no OWASP Top 10 vulnerabilities
  • Performance: no measurable regression introduced
  • Docs/changelog updated
  • Feature toggles/rollout considered
  • QA verified/UAT approved (if applicable)
  • Release notes prepared; monitoring/alerts set

Activity

  1. linear-code commented on Jul 24, 2026

    @linear-code
  2. added this to the v1.0 milestone on Jul 24, 2026
  3. github-actions commented on Jul 24, 2026

    @github-actions
    Contributor

    ⚠️ This issue does not follow a required issue template.

    Missing required section(s): Definition of Ready (DoR), Definition of Done (DoD)

    The issue will remain open and flagged until the body is corrected.
    Please update the issue with one of the official templates:

    If this was opened by automation, update the automation to preserve the template sections before creating the issue.

  4. github-actions commented on Jul 24, 2026

    @github-actions
    Contributor

    ⏱️ Aging and SLA annotation

    • Age: 12 day(s)
    • SLA state: SLA risk
    • Thresholds: warn at 7 days, breach at 14 days
    • Last updated: 2026-08-05T11:16:49.778Z

    Maintained by project-meta-sync workflow.

  5. 12 remaining items

  6. changed the title [-]Create permanent maintenance documentation (BRANCH_CLEANUP.md + MAINTENANCE.md)[/-] [+]docs: repository-maintenance - Align branch cleanup runbooks[/+] on Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Fields

Priority

None yet

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions