Skip to content

fix: Wave 5 Phase 2 #660 issue-type parity across canonical configs#788

Open
ashleyshaw wants to merge 1 commit into
developfrom
claude/wave-5-phase2-660-type-parity
Open

fix: Wave 5 Phase 2 #660 issue-type parity across canonical configs#788
ashleyshaw wants to merge 1 commit into
developfrom
claude/wave-5-phase2-660-type-parity

Conversation

@ashleyshaw
Copy link
Copy Markdown
Member

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-

@lightspeedwp/github-community-health@0.5.0 lint:yaml
spectral lint '**/*.{yml,yaml}' --ruleset .spectral.config.cjs

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

Synchronise type mappings between .github/issue-fields.yml, .github/issue-types.yml, and .github/labels.yml for Wave 5 Phase 2 (#660).
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 3, 2026

Warning

Review limit reached

@ashleyshaw, we couldn't start this review because you've reached your PR review rate limit.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 5ffc1b00-39fc-436a-9e4b-08b6abf0ce06

📥 Commits

Reviewing files that changed from the base of the PR and between 073116f and cb41fd6.

📒 Files selected for processing (3)
  • .github/issue-fields.yml
  • .github/issue-types.yml
  • .github/labels.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/wave-5-phase2-660-type-parity

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 github-actions Bot added area:labels Label governance and routing status:needs-review Awaiting code review priority:normal Default priority labels Jun 3, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 3, 2026

🔍 Reviewer Summary for PR #788

CI Status:success
Files changed: 3
Risk Distribution: 0 critical, 3 high, 0 medium, 0 low

Recommendations

  • Ready to proceed pending human review

@github-actions github-actions Bot added type:chore Chore / small hygiene change type:bug Bug or defect meta:needs-changelog Requires a changelog entry before merge labels Jun 3, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread .github/labels.yml
Comment on lines +125 to +127
- name: type:ui
color: AB7DF8
description: "UI implementation and consistency"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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

Comment thread .github/labels.yml
Comment on lines +141 to +143
- name: type:enhancement
color: 9198A1
description: "Enhancement to existing capability"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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

Comment thread .github/labels.yml
Comment on lines +153 to +155
- name: type:ci
color: 4393F8
description: "CI/CD pipeline work"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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 ci alias to the type:ci label.

- name: type:ci
  color: 4393F8
  description: "CI/CD pipeline work"
  aliases:
    - ci

Comment thread .github/labels.yml
Comment on lines +169 to +171
- name: type:qa
color: D29922
description: "Quality assurance work"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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 qa alias to the type:qa label.

- name: type:qa
  color: D29922
  description: "Quality assurance work"
  aliases:
    - qa

Comment thread .github/labels.yml
Comment on lines +193 to +195
- name: type:dependency
color: 8D4821
description: "Dependency management and updates"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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

Comment thread .github/labels.yml
Comment on lines +221 to +223
- name: type:investigation
color: 9198A1
description: "Investigation and root-cause analysis"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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:
    - investigation

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread .github/labels.yml
Comment on lines +193 to +195
- name: type:dependency
color: 8D4821
description: "Dependency management and updates"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:labels Label governance and routing meta:needs-changelog Requires a changelog entry before merge priority:normal Default priority status:needs-review Awaiting code review type:bug Bug or defect type:chore Chore / small hygiene change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant