[Epic] Label governance stabilisation and automation hardening by ashleyshaw · Pull Request #436 · lightspeedwp/.github

ashleyshaw · 2026-05-27T16:25:10Z

name: "📦 Epic"
about: "Propose/manage a large, multi-part initiative or project grouping stories/features/tasks"
title: "[Epic] Label governance stabilisation and automation hardening"
labels: [status:needs-planning, priority:important, area:core, type:epic, type:automation]

Epic Summary

Stabilise repository label governance by resolving orphan labels, aligning canonical label definitions, and hardening workflow policies that depend on label metadata.

This epic groups the follow-on work scaffolded in PR #436 into a single execution track so planning, sequencing, and delivery are explicit and maintainable.

Linked Stories/Tasks

🏷️ Orphan Labels Detected (30) #95 Orphan labels audit and remediation
[Workflows/Docs] Canonical labels + org seeding workflow #66 Canonical labels and seeding workflow alignment
[Workflows] Scope README regen to changed paths with concurrency guard #67 README regeneration scoping and concurrency guard
[Workflows] Enforce CodeRabbit before Copilot on PRs #69 CodeRabbit-before-Copilot review order enforcement

Milestones & Timeline

Phase 1: Audit current orphan labels and produce remediation plan from 🏷️ Orphan Labels Detected (30) #95
Phase 2: Execute canonical label and seeding updates in [Workflows/Docs] Canonical labels + org seeding workflow #66
Phase 3: Harden README regeneration scope and concurrency behaviour in [Workflows] Scope README regen to changed paths with concurrency guard #67
Phase 4: Implement and validate review-order policy in [Workflows] Enforce CodeRabbit before Copilot on PRs #69

Suggested sequence:

🏷️ Orphan Labels Detected (30) #95 first
[Workflows/Docs] Canonical labels + org seeding workflow #66 and [Workflows] Scope README regen to changed paths with concurrency guard #67 in parallel once audit output is confirmed
[Workflows] Enforce CodeRabbit before Copilot on PRs #69 in parallel if workflow ownership is available

Acceptance Criteria

Orphan label inventory is current and documented
Canonical label source of truth is aligned with seeding automation
README regeneration is scoped to relevant paths and protected against concurrent conflicts
Review-order policy is explicit, testable, and reflected in workflow behaviour
Linked stories/tasks are sequenced and tracked from this epic
Documentation and changelog updated where policy-visible
Tests/QA complete
Milestone closed

Dependencies / Blockers

Requires current orphan label evidence and decision table from 🏷️ Orphan Labels Detected (30) #95 before final canonical clean-up
Workflow changes must be validated with repo-supported local and CI checks
Review-order enforcement may depend on existing PR workflow constraints and maintainer policy decisions

Additional Context

This epic was scaffolded from PR #436:

PR [Epic] Label governance stabilisation and automation hardening #436 adds the workstream pack at .github/projects/active/label-governance-stabilisation-2026-05-27/
It includes the parent epic draft, child issue drafts, and the posting/linking plan
The goal is to keep the approach issue-first and modular before implementation work begins

Related workstream path:

.github/projects/active/label-governance-stabilisation-2026-05-27/

Definition of Ready (DoR)

Epic goal and scope defined
Linked stories/tasks listed
Milestones and timeline mapped
Dependencies/blockers identified
Estimate added (if applicable)
Stakeholders/approvers listed

Definition of Done (DoD)

All linked stories/tasks completed and closed
Documentation/changelog updated
QA and testing complete
Milestone closed and release notes prepared

coderabbitai · 2026-05-27T16:25:18Z

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: cb9b4934-dd02-46a8-a1f8-784543f6cfd0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Note

`.coderabbit.yml` has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)

Validation error: Unrecognized keys: "auto_labels", "auto_assign", "auto_review"

⚙️ Configuration instructions

Please see the configuration documentation for more information.
You can also validate your configuration using the online YAML validator.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch codex/next-workstream-label-governance-2026-05-27

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

github-actions · 2026-05-27T16:26:02Z

🔍 Reviewer Summary for PR #436

CI Status: ✅ success
Files changed: 8

Recommendations

Ready to proceed pending human review

gemini-code-assist

Code Review

This pull request introduces a new project workstream for "Label Governance Stabilisation," including a planning README, an issue posting and linking plan, and draft templates for parent epics and child tasks (issues #95, #66, #67, and #69). The review feedback highlights that several draft issue templates violate the labeling agent's 'one-hot' constraint by applying multiple type: labels, and provides suggestions to retain only one primary type: label per file. Additionally, it is recommended to document any resulting label migration maps in the central /docs/MIGRATION.md file.

gemini-code-assist · 2026-05-27T16:26:21Z

+
+Create a single, issue-first execution pack that:
+
+- Reduces orphan labels to zero or a justified minimal set.


Since this workstream involves reducing orphan labels and defining remediation/migration steps, please ensure that any resulting label migration maps and notes are documented in the central /docs/MIGRATION.md file to ensure contributors can follow migration rules across the repository.

References

Document migration maps and notes in a central /docs/MIGRATION.md file to ensure contributors can follow migration rules mentioned in README files across the repository.

gemini-code-assist · 2026-05-27T16:26:21Z

+name: "Audit"
+about: "Audit orphan labels and define remediation for issue #95"
+title: "[Audit] Reconcile orphan labels and remediation plan (#95)"
+labels: [status:needs-audit, priority:important, type:audit, area:ci, type:automation]


The labeling agent (scripts/agents/labeling.agent.js) enforces a 'one-hot' constraint on type: labels (meaning only one label starting with type: should be applied). This draft has multiple type: labels (type:audit and type:automation), which violates this constraint and will cause the automation to strip or conflict on them. Please keep only one primary type: label.

Suggested change

labels: [status:needs-audit, priority:important, type:audit, area:ci, type:automation]

labels: [status:needs-audit, priority:important, type:audit, area:ci]

gemini-code-assist · 2026-05-27T16:26:21Z

+name: "Task"
+about: "Execute canonical label and seeding workflow hardening for issue #66"
+title: "[Task] Canonical labels plus org seeding workflow alignment (#66)"
+labels: [status:ready, priority:important, type:task, area:ci, type:automation, type:documentation]


The labeling agent (scripts/agents/labeling.agent.js) enforces a 'one-hot' constraint on type: labels. This draft has multiple type: labels (type:task, type:automation, and type:documentation), which violates this constraint. Please keep only one primary type: label.

Suggested change

labels: [status:ready, priority:important, type:task, area:ci, type:automation, type:documentation]

labels: [status:ready, priority:important, type:task, area:ci]

gemini-code-assist · 2026-05-27T16:26:21Z

+name: "Task"
+about: "Implement scoped README regeneration and concurrency guard for issue #67"
+title: "[Task] Scope README regeneration and add concurrency guard (#67)"
+labels: [status:ready, priority:important, type:task, area:ci, type:documentation]


The labeling agent (scripts/agents/labeling.agent.js) enforces a 'one-hot' constraint on type: labels. This draft has multiple type: labels (type:task and type:documentation), which violates this constraint. Please keep only one primary type: label.

Suggested change

labels: [status:ready, priority:important, type:task, area:ci, type:documentation]

labels: [status:ready, priority:important, type:task, area:ci]

gemini-code-assist · 2026-05-27T16:26:21Z

+name: "Task"
+about: "Enforce review-order policy in workflows for issue #69"
+title: "[Task] Enforce CodeRabbit before Copilot in PR workflow policy (#69)"
+labels: [status:needs-triage, priority:important, type:task, area:ci, type:automation]


The labeling agent (scripts/agents/labeling.agent.js) enforces a 'one-hot' constraint on type: labels. This draft has multiple type: labels (type:task and type:automation), which violates this constraint. Please keep only one primary type: label.

Suggested change

labels: [status:needs-triage, priority:important, type:task, area:ci, type:automation]

labels: [status:needs-triage, priority:important, type:task, area:ci]

gemini-code-assist · 2026-05-27T16:26:21Z

+name: "Epic"
+about: "Stabilise repository label governance and automation contracts"
+title: "[Epic] Label governance stabilisation and automation hardening"
+labels: [status:needs-planning, priority:important, type:epic, area:ci, type:automation]


The labeling agent (scripts/agents/labeling.agent.js) enforces a 'one-hot' constraint on type: labels. This draft has multiple type: labels (type:epic and type:automation), which violates this constraint. Please keep only one primary type: label.

Suggested change

labels: [status:needs-planning, priority:important, type:epic, area:ci, type:automation]

labels: [status:needs-planning, priority:important, type:epic, area:ci]

docs(governance): scaffold label governance stabilisation workstream

3eb40fc

github-actions Bot added migrate:status:needs-review Awaiting code review migrate:priority:normal Default priority migrate:type:chore Chore / small hygiene change migrate:type:documentation Documentation migrate:meta:needs-changelog Requires a changelog entry before merge labels May 27, 2026

gemini-code-assist Bot reviewed May 27, 2026

View reviewed changes

ashleyshaw merged commit 29013e1 into develop May 27, 2026
11 of 12 checks passed

ashleyshaw deleted the codex/next-workstream-label-governance-2026-05-27 branch May 27, 2026 16:36

ashleyshaw changed the title ~~docs(governance): scaffold label governance stabilisation workstream~~ [Epic] Label governance stabilisation and automation hardening May 27, 2026

github-actions Bot removed the migrate:type:chore Chore / small hygiene change label May 27, 2026

Navigation Menu

Repository navigation

[Epic] Label governance stabilisation and automation hardening - #436

[Epic] Label governance stabilisation and automation hardening#436
ashleyshaw merged 1 commit into
developfrom
codex/next-workstream-label-governance-2026-05-27

ashleyshaw commented May 27, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented May 27, 2026

Review skipped

`.coderabbit.yml` has unrecognized properties

Uh oh!

github-actions Bot commented May 27, 2026

Uh oh!

gemini-code-assist Bot left a comment

Uh oh!

gemini-code-assist Bot May 27, 2026

Uh oh!

gemini-code-assist Bot May 27, 2026

Uh oh!

gemini-code-assist Bot May 27, 2026

Uh oh!

gemini-code-assist Bot May 27, 2026

Uh oh!

gemini-code-assist Bot May 27, 2026

Uh oh!

gemini-code-assist Bot May 27, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant


		Create a single, issue-first execution pack that:

		- Reduces orphan labels to zero or a justified minimal set.

	labels: [status:needs-audit, priority:important, type:audit, area:ci, type:automation]
	labels: [status:needs-audit, priority:important, type:audit, area:ci]

	labels: [status:ready, priority:important, type:task, area:ci, type:automation, type:documentation]
	labels: [status:ready, priority:important, type:task, area:ci]

	labels: [status:needs-triage, priority:important, type:task, area:ci, type:automation]
	labels: [status:needs-triage, priority:important, type:task, area:ci]

	labels: [status:needs-planning, priority:important, type:epic, area:ci, type:automation]
	labels: [status:needs-planning, priority:important, type:epic, area:ci]

Conversation

ashleyshaw commented May 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

name: "📦 Epic" about: "Propose/manage a large, multi-part initiative or project grouping stories/features/tasks" title: "[Epic] Label governance stabilisation and automation hardening" labels: [status:needs-planning, priority:important, area:core, type:epic, type:automation]

Epic Summary

Linked Stories/Tasks

Milestones & Timeline

Acceptance Criteria

Dependencies / Blockers

Additional Context

Definition of Ready (DoR)

Definition of Done (DoD)

Uh oh!

coderabbitai Bot commented May 27, 2026

Review skipped

.coderabbit.yml has unrecognized properties

Uh oh!

github-actions Bot commented May 27, 2026

🔍 Reviewer Summary for PR #436

Recommendations

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist Bot May 27, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot May 27, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot May 27, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot May 27, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot May 27, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot May 27, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

ashleyshaw commented May 27, 2026 •

edited

Loading

name: "📦 Epic"
about: "Propose/manage a large, multi-part initiative or project grouping stories/features/tasks"
title: "[Epic] Label governance stabilisation and automation hardening"
labels: [status:needs-planning, priority:important, area:core, type:epic, type:automation]

`.coderabbit.yml` has unrecognized properties