Repository navigation
Description
Is your code refactoring request related to a problem?
Three workflows share the issues: [closed] trigger and all deal with issue compliance, causing duplicate GitHub API calls on every issue close event:
template-enforcement.yml(388 lines) — validates issue template completeness on open/edit/reopen/closechecklist-finalisation.yml(222 lines) — marks checklist items, updates project fields on closevalidate-issue-dod-before-close.yml(113 lines) — validates DoD checkboxes before allowing close
Each fires independently on issues: [closed], resulting in 3 separate workflow runs for the same event. There is no single authoritative location for issue closure governance.
Part of epic #1227 — Workflows Consolidation Initiative.
Describe the Refactoring / Review Task
Create .github/workflows/issue-compliance.yml consolidating all three with conditional job guards:
on:
issues:
types: [opened, edited, reopened, closed]
pull_request_target:
types: [closed]
push:
branches: [develop]
jobs:
enforce-template:
if: github.event.action != 'closed' || github.event_name == 'push'
validate-dod-on-close:
if: github.event.action == 'closed' && github.event_name == 'issues'
finalise-checklists:
if: github.event.action == 'closed'No behaviour change — all existing logic preserved. Net: −2 workflows (3 files → 1).
Use Case
- Single source of truth for issue compliance lifecycle events
- Eliminates 3× duplicate workflow runs on every issue close
- Easier to extend (one file, not three)
- Reduces GitHub Actions minutes
Alternatives Considered
- Extend
template-enforcement.yml: Would exceed 700 lines — too large - Keep as-is: Continues duplicate API calls and fragmented governance
Additional Context
Blocker: Phase 3.3 must complete first (or can run in parallel — no code dependency on labeling work).
DoD/close-loop safety: issue-compliance.yml and issue-health-audit.yml do not create a close/reopen loop — health audit runs on a weekly schedule only.
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
- Phase 3.3 complete (blocker resolved)
- Estimate added
Definition of Done (DoD)
-
issue-compliance.ymlcreated with all three jobs properly conditioned - All original behaviours verified (open, edit, close integration tests)
-
template-enforcement.yml,checklist-finalisation.yml,validate-issue-dod-before-close.ymldeleted - No regressions in issue labeling or project field updates
- 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-1959
github-actions commentedon Jul 29, 2026
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow.
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.
refactor: consolidate issue-close governance workflows into issue-com…
refactor: consolidate issue-close governance workflows into issue-com…
refactor: consolidate issue-close governance workflows into issue-com…
github-actions commentedon Sep 4, 2026
Milestone Allocation
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.