fix: Wave 5 Phase 2 #660 issue-type parity across canonical configs#788
fix: Wave 5 Phase 2 #660 issue-type parity across canonical configs#788ashleyshaw wants to merge 1 commit into
Conversation
Synchronise type mappings between .github/issue-fields.yml, .github/issue-types.yml, and .github/labels.yml for Wave 5 Phase 2 (#660).
|
Warning Review limit reached
More reviews will be available in 4 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
🔍 Reviewer Summary for PR #788CI Status: ✅ Recommendations
|
There was a problem hiding this comment.
Code Review
This pull request updates the GitHub issue configuration files (issue-fields.yml, issue-types.yml, and labels.yml) to introduce several new issue types and labels, including ui, enhancement, ci, qa, dependency, and investigation. The review feedback recommends adding corresponding aliases to these new labels in labels.yml to ensure consistency and support proper mapping by the label standardization agent.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| - name: type:ui | ||
| color: AB7DF8 | ||
| description: "UI implementation and consistency" |
There was a problem hiding this comment.
To maintain consistency with other canonical type labels and ensure the label standardization agent can correctly map non-prefixed labels to their canonical versions, please add the ui alias to the type:ui label.
- name: type:ui
color: AB7DF8
description: "UI implementation and consistency"
aliases:
- ui| - name: type:enhancement | ||
| color: 9198A1 | ||
| description: "Enhancement to existing capability" |
There was a problem hiding this comment.
To maintain consistency with other canonical type labels and ensure the label standardization agent can correctly map non-prefixed labels to their canonical versions, please add the enhancement alias to the type:enhancement label.
- name: type:enhancement
color: 9198A1
description: "Enhancement to existing capability"
aliases:
- enhancement| - name: type:ci | ||
| color: 4393F8 | ||
| description: "CI/CD pipeline work" |
There was a problem hiding this comment.
| - name: type:qa | ||
| color: D29922 | ||
| description: "Quality assurance work" |
There was a problem hiding this comment.
| - name: type:dependency | ||
| color: 8D4821 | ||
| description: "Dependency management and updates" |
There was a problem hiding this comment.
To maintain consistency with other canonical type labels and ensure the label standardization agent can correctly map non-prefixed labels to their canonical versions, please add the dependency and dependencies aliases to the type:dependency label.
- name: type:dependency
color: 8D4821
description: "Dependency management and updates"
aliases:
- dependency
- dependencies| - name: type:investigation | ||
| color: 9198A1 | ||
| description: "Investigation and root-cause analysis" |
There was a problem hiding this comment.
To maintain consistency with other canonical type labels and ensure the label standardization agent can correctly map non-prefixed labels to their canonical versions, please add the investigation alias to the type:investigation label.
- name: type:investigation
color: 9198A1
description: "Investigation and root-cause analysis"
aliases:
- investigationThere was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cb41fd602d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - name: type:dependency | ||
| color: 8D4821 | ||
| description: "Dependency management and updates" |
There was a problem hiding this comment.
Wire dependency detection to the new canonical label
When a dependency issue or PR relies on the labeling agent's automatic detection, this new singular type:dependency label is never applied: scripts/agents/labeling.agent.js still maps dependency, dependencies, and deps/ to the plural type:dependencies, which is not in the canonical label set and is therefore skipped. That leaves dependency work classified by the default/fallback type instead of the canonical type this change adds.
Useful? React with 👍 / 👎.
Summary\nThis PR implements the Phase 2 follow-on for Wave 5 issue #660 by enforcing type-parity across canonical config files.\n\n## Changes\n- Added missing canonical type entries to \n- Added matching type labels to \n- Added and mappings to \n\n## Validation\n- ✅ Issue-fields config YAML parsed and required structure is valid
✅ docs/ISSUE_FIELDS.md references canonical mappings and profile keys ✅\n-
No results with a severity of 'error' found! ✅\n- Cross-file parity check (issue-fields vs issue-types vs labels) ✅ (0 mismatches)\n\n## Related\n- https://github.com/lightspeedwp/.github/issues/660\n- Complements Phase 1 audit deliverable at: https://github.com/lightspeedwp/.github/blob/develop/.github/reports/audits/2026-06-03-issue-fields-config-vs-github-api-audit-660.md