Skip to content

feat: Consolidate 31 GitHub workflows for efficiency and maintainability #1227

Open
9 of 17 issues completed
Open

Description

@ashleyshaw

feat: Consolidate 31 GitHub workflows for efficiency and maintainability

Epic Overview

Comprehensive consolidation of GitHub workflows across the .github repository to address technical debt through code deduplication, redundancy elimination, and scheduling optimization.

Outcome: Reduce workflow count from 31 to 25 (19% reduction), eliminate ~500 lines of duplicated code, and save 15-20% GitHub Actions minutes while improving maintainability.

Status: 🟡 IN PROGRESS

  • ✅ Phase 1A: Quick Wins - COMPLETE
  • ✅ Phase 1B: Medium-Impact - COMPLETE
  • 🟡 Phase 2: Documentation Consolidation - IN PROGRESS
  • 📋 Phase 3: Labeling - READY TO START
  • 📋 Phase 4: Future - PLANNING

Phase 2: Documentation Consolidation (Current)

PR: #1306 - Phase 2 Implementation
Status: Ready for merge - all planning and implementation complete

Phase 2 Work Items

Issue Title Status PR
#1307 Create docs-validation.yml ✅ COMPLETED #1306
#1308 Create docs-maintenance.yml ✅ COMPLETED #1306
#1309 Integration Testing 🟡 READY #1306
#1310 Cleanup Old Workflows 🔴 BLOCKED #1306
#1311 Code Review & Merge 🟡 IN PROGRESS #1306

Phase 2 Scope:

  • Consolidate 4 documentation workflows into 2 streamlined workflows
  • Eliminate ~150 lines of duplication
  • Save ~40 GitHub Actions minutes/week
  • Effort: 12-16 hours total

Deliverables:

  • ✅ docs-validation.yml (PR validation: Mermaid + README)
  • ✅ docs-maintenance.yml (Scheduled/manual maintenance)
  • ✅ Planning documents (PHASE_2_EXECUTION.md, PHASE_2_ISSUES.md)
  • ✅ Integration test plan (PHASE_2_2_TEST_RESULTS.md)
  • ✅ Legacy workflow deprecation markers

Key Resources

Project Folder: .github/projects/active/workflows-consolidation-2026-q3/

  • README.md - Navigation hub & quick facts
  • IMPLEMENTATION_SUMMARY.md - Executive overview
  • EXECUTION_PLAYBOOK.md - Step-by-step implementation guide
  • PROJECT_INDEX.md - Complete file navigation
  • PHASE_2_EXECUTION.md - Phase 2 detailed execution plan
  • PHASE_2_ISSUES.md - Phase 2 issue templates
  • PHASE_2_2_TEST_RESULTS.md - Integration test scenarios

Audit Report: .github/reports/workflows/WORKFLOWS-CONSOLIDATION-AUDIT.md

Success Metrics

Phase 1 Results: ✅ COMPLETE

  • ✅ Quick wins: Deleted testing.yml (85 lines)
  • ✅ Changelog consolidation: Reduced duplication
  • ✅ Metrics consolidation: Unified reporting

Phase 2 Results: 🟡 IN PROGRESS

  • ✅ 4 workflows → 2 workflows (50% reduction)
  • ✅ ~150 lines duplication eliminated
  • ✅ ~40 GHA minutes/week saved
  • ✅ All validation logic preserved
  • ✅ Conditional job structure proven

Overall Goal Tracking:

  • Workflows: 31 → 25 (6 reduction needed, 2 done) = 67% of target
  • Code lines: ~500 to eliminate, ~150 done = 30% progress
  • GHA minutes: 15-20% reduction goal, 8-10% achieved = in progress

Timeline

Phase Duration Effort Status
1A: Quick Wins Week 1 4h ✅ COMPLETE
1B: Medium-Impact Weeks 2-3 14-20h ✅ COMPLETE
2: Documentation Weeks 5-8 12-16h 🟡 IN PROGRESS
3: Labeling Weeks 5-8 6-8h 📋 READY
4: Future Month 3+ TBD 📋 PLANNING

Related Links


Epic Owner: Ash Shaw
Last Updated: 2026-07-24
Next Milestone: Phase 2.2 Integration Testing (Issue #1309)


Definition of Ready (DoR)

  • Epic vision and scope clearly defined
  • Success criteria and measurable outcomes documented
  • High-level tasks/stories identified
  • Dependencies and risks mapped
  • Timeline and resource estimates provided
  • Stakeholder alignment confirmed

Epic Owner / Sponsor

Sponsor/Owner: [Who is driving this epic]

Success Owner: [Who validates completion]

Success Criteria

  • All Phase milestones achieved
  • Stakeholder sign-off obtained
  • Team capacity and velocity met targets

Definition of Done (DoD)

  • All child issues/stories completed
  • Epic acceptance criteria met
  • Epic documentation and summary updated
  • Release notes and announcement prepared
  • Post-launch monitoring and support plan in place
  • Retrospective completed (if applicable)

Activity

  1. linear-code commented on Jul 24, 2026

    @linear-code
  2. github-actions commented on Jul 24, 2026

    @github-actions
    Contributor

    ✅ Template check passed after update. Thanks for fixing the issue body.

  3. added this to the v1.0 milestone on Jul 24, 2026
  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:18:43.864Z

    Maintained by project-meta-sync workflow.

  5. 74 remaining items

  6. ashleyshaw commented on Aug 7, 2026

    @ashleyshaw
    MemberAuthor

    🎯 Phase 4 Planning Complete — PR #1631 Merged

    Summary

    All Phase 4 planning documentation, specifications, and coordination timelines have been completed and merged to develop (commit ac5c8de).

    Deliverables (Merged in PR #1631)

    • ✅ AUDIT_2026_08_07_COMPREHENSIVE.md — Current state (41 workflows)
    • ✅ OPENSPEC_WORKFLOW_CONSOLIDATION.md — Formal specification (41→25)
    • ✅ OPENSPEC_MULTIPROJECT_ANALYSIS_2026_08_07.md — Cross-project alignment (11 projects)
    • ✅ CONSOLIDATED_ACTION_PLAN_2026_08_07.md — Execution timeline (Aug 8-25)
    • ✅ GITHUB_ISSUES_PHASE_4_TEMPLATES.md — Ready-to-execute issue templates
    • ✅ PHASE_4_EXECUTION_READY_SUMMARY.md — Executive summary for stakeholders

    Phase 4 Issues Ready for Execution

    Execution Timeline

    Blocking Dependencies Identified

    1. Issue Type & Metadata Automation (Phase 1) — Target Aug 13
    2. Release Process Redesign — Coordination by Aug 12
    3. GitHub Projects Creation System — Clarification by Aug 12

    Status: Ready for Phase 4 execution. All planning complete, issues assigned, timeline established.

  7. github-actions commented on Sep 8, 2026

    @github-actions
    Contributor

    ⚠️ Bare Labels Detected

    This issue has labels that are not in the canonical taxonomy:

    • migrate:status:needs-more-info
    • migrate:area:infrastructure
    • migrate:type:epic
    • priority:high

    Valid Canonical Labels

    Please use labels with a prefix from the canonical taxonomy:

    • Type: type:bug, type:feature, type:task, type:documentation, etc.
    • Status: status:needs-triage, status:in-progress, status:done, etc.
    • Priority: priority:critical, priority:high, priority:normal, priority:low
    • Area: area:ci, area:docs, area:labels, area:security, etc.
    • Meta: meta:needs-changelog, meta:duplicate, meta:blocked, etc.

    For the complete list, see .github/labels.yml.

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

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions