Skip to content

Phase 4.6: Consolidate issue-remediation-bulk.yml + issue-health-audit.yml into issue-audit-remediation.yml #1411

Description

@ashleyshaw

Is your code refactoring request related to a problem?

Two workflows added on 2026-07-29 (PR #1377 and PR #1399) both perform bulk issue label remediation and compliance checks, creating a conceptual overlap:

  • issue-remediation-bulk.yml (260 lines) — workflow_dispatch; remediates last N days of issues: auto-assigns milestones, adds missing type labels, posts template remediation checklists
  • issue-health-audit.yml (267 lines) — weekly schedule + workflow_dispatch; reopens issues closed with unchecked DoD items; applies missing type/priority labels

Both apply missing type:/priority: labels to open issues. Running them independently can cause redundant API calls and inconsistent remediation behaviour if both fire close together.

Part of epic #1227 — Workflows Consolidation Initiative. Net: −1 workflow.

Describe the Refactoring / Review Task

Create .github/workflows/issue-audit-remediation.yml combining both workflows:

on:
  schedule:
    - cron: "0 8 * * 1"  # Weekly Monday (from health-audit)
  workflow_dispatch:
    inputs:
      mode:
        description: 'Operation mode'
        type: choice
        options:
          - audit        # Reopen closed issues with unchecked DoD (from health-audit)
          - remediate    # Fix labels/milestones/templates (from remediation-bulk)
          - full         # Run both
      days:
        description: 'Scope: issues created in last N days (remediate mode)'
      dry_run:
        default: 'true'

No behaviour change — all operations preserved, unified entry point. Net: −1 workflow.

Use Case

  • Single workflow for all scheduled and on-demand issue compliance remediation
  • Consistent dry-run support across both operations
  • Clearer operator UX: one workflow_dispatch to trigger any remediation task
  • Reduces confusion about which workflow to run for label/DoD remediation

Alternatives Considered

  • Keep separate: Both are functional as-is; consolidation is a quality-of-life improvement not a bug fix
  • Delete remediation-bulk entirely: Would lose the targeted N-day scoping feature

Additional Context

Interaction with metadata-governance.yml: When issue-audit-remediation.yml applies a type: label, metadata-governance.yml triggers on the labeled event and syncs the native issue type. This is the expected chain — no conflict.

Dependency: Independent of other Phase 4 sub-phases.

See: .github/projects/active/workflows-consolidation-2026-q3/PHASE_4_PLANNING.md


Definition of Ready (DoR)

  • Refactoring goals and scope defined
  • Code area(s) and impact listed
  • Dependencies mapped (independent)
  • Estimate added
  • Both source workflows confirmed stable in production

Definition of Done (DoD)

  • issue-audit-remediation.yml created with audit, remediate, and full modes
  • Dry-run mode verified for all modes before first live run
  • issue-remediation-bulk.yml and issue-health-audit.yml deleted
  • Weekly schedule preserved (Monday 8 AM UTC)
  • Integration test: label application triggers metadata-governance.yml native type sync
  • Code meets org coding standards
  • Changelog entry prepared (CHANGELOG.md)
  • PR uses correct branch prefix (refactor/)

Activity

  1. linear-code commented on Jul 29, 2026

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

    @github-actions
    Contributor

    ⏱️ Aging and SLA annotation

    • Age: 8 day(s)
    • SLA state: SLA risk
    • Thresholds: warn at 7 days, breach at 14 days
    • Last updated: 2026-08-07T14:36:15.559Z

    Maintained by project-meta-sync workflow.

  3. added theissue type on Aug 7, 2026
  4. added this to the v1.0 milestone on Aug 7, 2026
  5. self-assigned this
    on Aug 7, 2026
  6. ashleyshaw commented on Aug 7, 2026

    @ashleyshaw
    MemberAuthor

    ✅ Phase 4 planning complete: PR #1631 merged to develop

    All Phase 4 planning documents, specifications, and coordination timelines are now available in the merged PR. This issue is ready for execution per the CONSOLIDATED_ACTION_PLAN_2026_08_07.md timeline.

    See merged PR #1631 for:

    • OPENSPEC_WORKFLOW_CONSOLIDATION.md (formal specification)
    • CONSOLIDATED_ACTION_PLAN_2026_08_07.md (execution timeline & blockers)
    • GITHUB_ISSUES_PHASE_4_TEMPLATES.md (implementation steps)
    • Detailed risk mitigation and testing protocols

    Status: Ready for execution. Refer to coordination deadlines in action plan.

  7. ashleyshaw commented on Aug 7, 2026

    @ashleyshaw
    MemberAuthor

    📋 Project Planning Update — workflows-consolidation-2026-q3

    This issue is related to the workflows-consolidation-2026-q3 active project.

    📁 Project Documentation

    ✅ Phase 1-3 Summary

    Comprehensive audits (Phase 1), planning standardization (Phase 2), and OpenSpec RFC generation (Phase 3) have been completed for this project. Full documentation available in the project directory.

    🎯 Recommended Actions

    1. Review Project Documentation for overview and timeline
    2. Consult OpenSpec RFC for implementation roadmap
    3. Check Related Issues for dependencies and prerequisites
    4. Reference Phase Documents for specific execution guidance

    🔗 Quick Links


    Co-Authored-By: Claude Haiku 4.5 noreply@anthropic.com

  8. modified the milestones: v1.0, v1.1 on Aug 29, 2026
  9. github-actions commented on Sep 4, 2026

    @github-actions
    Contributor

    Milestone Allocation

    
    
  10. github-actions commented on Sep 4, 2026

    @github-actions
    Contributor

    ⚠️ This issue was closed but the Definition of Done (DoD) is not complete.

    Unchecked DoD items found. Please complete all checklist items before closing this issue.

    To close this issue:

    • ✅ Complete all DoD checklist items and check them off
    • 🔁 Close the issue again

    To force close this issue without completing DoD:

    • Add the meta:force-close label
    • The system will then allow closure

    For more information on Definition of Done standards, see the issue template guide: https://github.com/lightspeedwp/.github/issues/new/choose

  11. github-actions commented on Sep 4, 2026

    @github-actions
    Contributor

    ✅ Issue checklists finalised after closure.

  12. 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:ready
    • migrate:type:refactor
    • priority:medium
    • status:ready-for-development

    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

Type

Fields

Priority

None yet

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions