Repository navigation
Description
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 checklistsissue-health-audit.yml(267 lines) — weeklyschedule+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.ymlcreated withaudit,remediate, andfullmodes - Dry-run mode verified for all modes before first live run
-
issue-remediation-bulk.ymlandissue-health-audit.ymldeleted - Weekly schedule preserved (Monday 8 AM UTC)
- Integration test: label application triggers
metadata-governance.ymlnative type sync - Code meets org coding standards
- Changelog entry prepared (CHANGELOG.md)
- PR uses correct branch prefix (
refactor/)
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
linear-code commentedon Jul 29, 2026
LS-1963
github-actions commentedon Jul 29, 2026
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow.
docs: Complete workflow consolidation Phase 4 audit and planning (#1631)
ashleyshaw commentedon Aug 7, 2026
✅ 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:
Status: Ready for execution. Refer to coordination deadlines in action plan.
ashleyshaw commentedon Aug 7, 2026
📋 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
🔗 Quick Links
Co-Authored-By: Claude Haiku 4.5 noreply@anthropic.com
refactor: consolidate issue-remediation-bulk + issue-health-audit int…
refactor: consolidate issue-remediation-bulk + issue-health-audit int…
refactor: consolidate issue-remediation-bulk + issue-health-audit int…
refactor: consolidate issue-remediation-bulk + issue-health-audit int…
github-actions commentedon Sep 4, 2026
Milestone Allocation
github-actions commentedon Sep 4, 2026
Unchecked DoD items found. Please complete all checklist items before closing this issue.
To close this issue:
To force close this issue without completing DoD:
meta:force-closelabelFor more information on Definition of Done standards, see the issue template guide: https://github.com/lightspeedwp/.github/issues/new/choose
github-actions commentedon Sep 4, 2026
✅ Issue checklists finalised after closure.
github-actions commentedon Sep 8, 2026
This issue has labels that are not in the canonical taxonomy:
migrate:status:readymigrate:type:refactorpriority:mediumstatus:ready-for-developmentValid Canonical Labels
Please use labels with a prefix from the canonical taxonomy:
type:bug,type:feature,type:task,type:documentation, etc.status:needs-triage,status:in-progress,status:done, etc.priority:critical,priority:high,priority:normal,priority:lowarea:ci,area:docs,area:labels,area:security, etc.meta:needs-changelog,meta:duplicate,meta:blocked, etc.For the complete list, see .github/labels.yml.