GitHub Tag Classification Refactor

[KJ7LNW]

GitHub Tag Classification Refactor

Tags Goal

When the migration is complete:

• All labels will use either issue/ or pr/ prefixes because it sorts nicely in the github tag selector, so you can find exactly what you need quickly specific to either an issue or pull request.
• No unprefixed labels will remain
• All labels will use consistent section/prefix:purpose format across both issues and PRs

Automation

• Some tags can be programmatically detected based on file paths and certain content changes.
• Automation for categorization should run at every push
• While AI could facilitate inspecting the pull request and adjusting the tags, the intention is for these to be added procedurally based on content so they should always be correct without AI fuzz.

Table of Contents

• GitHub Tag Classification Refactor

  • Tags Goal
    • Automation
  • Table of Contents
  • Updated PR Tags
    • Scope of Change Tags
    • Nature of Change Tags
  • Updated Issue Tags
  • Current GitHub Labels

• Label Migration Plan

  • Pull Request Label Mapping
  • Issue Label Mapping
  • Labels to Deprecate
  • Implementation Steps

PR Tags

Scope of Change Tags

Tag	Purpose	Detection Method
pr/scope:build	Build system, packaging, or automation scripts	Match files like esbuild.mjs, vite.config.ts, tsconfig.json
pr/scope:core	Changes to src/ (all non-webview code)	Match files within src/ excluding specialized directories
pr/scope:dev-ux	Developer-facing workflow changes	Match files like .eslintrc, CI configs, editor settings
pr/scope:doc	Documentation updates	Match files with .md extension or in doc directories
pr/scope:lang	i18n or l10n updates	Match changes to locales/, */i18n/*, or package.nls.*.json
pr/scope:newdeps	Adding or bumping dependencies	Parse package.json diff for dependency changes
pr/scope:prompts	Prompt-system structure and templates	Match files within src/core/prompts/
pr/scope:providers	LLM API integrations	Match files within src/api/providers/
pr/scope:settings	Application user settings	Match settings schema files or config registration code
pr/scope:test	Test code	Match files in __tests__/ or with test patterns
pr/scope:tools	Tool definitions or handlers	Match files within src/core/tools/
pr/scope:webview	UI/frontend tweaks	Match files within webview-ui/

Nature of Change Tags

Tag	Purpose	Detection Method
pr/prompts:force-feedback	Updates to feedback-driven prompts	Match changes to tool response mechanisms
pr/prompts:system	Changes to prompt-system logic	Match changes to system prompts and snapshots
pr/feature:default-off	Feature disabled by default	Developer selected
pr/feature:default-on	Feature enabled by default	Developer selected
pr/feature:enhancement	Improves existing feature	Developer selected
pr/fix:bug	Fix for non-critical issue	Developer selected
pr/fix:critical	Fix for blocking/security-critical bug	Developer selected
pr/fix:perf	Performance optimizations	Developer selected
pr/fix:security	Security vulnerability fixes	Developer selected
pr/refactor	Code restructuring	Developer selected

Issue Tags

These tags are used for Issues and are manually selected by users or maintainers.

Tag	Purpose
issue/bug	Report of incorrect behavior
issue/critical	High-priority blocking issue
issue/documentation	Missing or incorrect documentation
issue/enhancement	Improve existing functionality
issue/feature	Request for new functionality
issue/performance	Speed, memory, or efficiency issues
issue/question	General usage or implementation questions
issue/security	Security vulnerability or concern
issue/ui-ux	User interface or experience issues
issue/providers	Issues with LLM API integrations
issue/tools	Issues with specific tool functionality

Current GitHub Labels

The repository currently uses the following labels:

• actionable: Confirmed and ready to work on
• bug: Something isn't working
• changelog-ready: (No description)
• codex: (No description)
• documentation: Improvements or additions to documentation
• duplicate: This issue or pull request already exists
• enhancement: New feature or request
• feature request: Feature request, not a bug
• in progress: Actively being worked on
• lgtm: This PR has been approved by a maintainer
• needs change: (No description)
• Needs Discussion/Approval: Features and fixes that need discussion/approval
• needs information: Needs more information to be actionable
• needs scoping: Needs up-front scoping to be actionable
• question: Further information is requested
• size:XS/S/M/L/XL/XXL: PR size indicators
• support: Not verified as bug, currently just a support request
• UI/UX: UI/UX related or focused
• wontfix: This will not be worked on

Label Migration Plan

Based on analysis of current label usage across issues and pull requests, the following migration plan is recommended. Following the principle that labels used on both issues and PRs should be renamed to use the "issue/" prefix, while PR-specific labels will remain as-is or get new "pr/" prefixes.

Pull Request Label Mapping

New Label	Action	Source Label	Purpose
pr/changelog-ready	Rename	changelog-ready	For changelog inclusion
pr/feature:default-off	New	-	Feature disabled by default
pr/feature:default-on	New	-	Feature enabled by default
pr/feature:enhancement	New	-	Improves existing feature
pr/fix:bug	New	-	Fix for non-critical issue
pr/fix:critical	New	-	Fix for blocking/security-critical bug
pr/fix:perf	New	-	Performance optimizations
pr/fix:security	New	-	Security vulnerability fixes
pr/in-progress	New	-	Actively being worked on
pr/lgtm	Rename	lgtm	PR approval indicator
pr/need:change	New	-	Requires modifications
pr/need:discussion	New	-	Requires team input
pr/prompts:force-feedback	New	-	Updates to feedback-driven prompts
pr/prompts:system	New	-	Changes to prompt-system logic
pr/refactor	New	-	Code restructuring
pr/scope:build	New	-	Build system, packaging, or automation scripts
pr/scope:core	New	-	Changes to src/ (all non-webview code)
pr/scope:dev-ux	New	-	Developer-facing workflow changes
pr/scope:doc	New	-	Documentation updates
pr/scope:lang	New	-	i18n or l10n updates
pr/scope:newdeps	New	-	Adding or bumping dependencies
pr/scope:prompts	New	-	Prompt-system structure and templates
pr/scope:providers	New	-	LLM API integrations
pr/scope:settings	New	-	Application user settings
pr/scope:test	New	-	Test code
pr/scope:tools	New	-	Tool definitions or handlers
pr/scope:webview	New	-	UI/frontend tweaks
pr/size:XS	Rename	size:XS	PR changes 0-9 lines
pr/size:S	Rename	size:S	PR changes 10-29 lines
pr/size:M	Rename	size:M	PR changes 30-99 lines
pr/size:L	Rename	size:L	PR changes 100-499 lines
pr/size:XL	Rename	size:XL	PR changes 500-999 lines
pr/size:XXL	Rename	size:XXL	PR changes 1000+ lines

Issue Label Mapping

New Label	Action	Source Label	Purpose
issue/actionable	Rename	actionable	Confirmed and ready to work on
issue/bug	Rename	bug	Report of incorrect behavior
issue/documentation	Rename	documentation	Missing or incorrect documentation
issue/feature	Rename	feature request	Request for new functionality
issue/in-progress	Rename	in progress	Actively being worked on
issue/need:discussion	Rename	Needs Discussion/Approval	Requires team input
issue/need:information	Rename	needs information	Needs more details
issue/need:scoping	Rename	needs scoping	Requires planning
issue/performance	New	-	Speed, memory, or efficiency issues
issue/providers	New	-	Issues with LLM API integrations
issue/question	Rename	question	General usage or implementation questions
issue/security	New	-	Security vulnerability or concern
issue/support	Rename	support	Support requests
issue/tools	New	-	Issues with specific tool functionality
issue/ui-ux	Rename	UI/UX	User interface or experience issues
issue/wontfix:not-a-bug	New	-	Working as designed
issue/wontfix:not-planned	Rename	wontfix	Not prioritized at this time

Labels to Deprecate

Current Label	Reason
codex	Functionality-specific label, use issue tags instead
duplicate	Use GitHub's native duplicate linking instead
enhancement	Replace with more specific issue/feature
needs change	Replace with more specific issue/need:* labels

Implementation Steps

1. Create new PR tags:

   • Add all pr/scope:* tags for automated detection
   • Add all pr/feature:* and pr/fix:* tags for developer selection
   • Add all pr/need:* tags for workflow management

2. Rename existing labels:

   • Use GitHub API to rename all existing labels to their issue/ equivalents based on the mapping table
   • Script example:

     # For each label in the mapping table
     gh api --method PATCH /repos/RooVetGit/Roo-Cline/labels/bug \
       -f name="issue/bug" -f color="d73a4a" -f description="Something isn't working"
     

3. Convert PR-specific labels:

   • Rename PR-specific labels to use the pr/ prefix
   • For example: lgtm → pr/lgtm
   • Script example:

     gh api --method PATCH /repos/RooVetGit/Roo-Cline/labels/lgtm \
       -f name="pr/lgtm" -f color="238636" -f description="This PR has been approved by a maintainer"
     

4. Deprecate obsolete labels:

   • Remove codex, enhancement, needs change, and duplicate labels
   • Script example:

     gh api --method DELETE /repos/RooVetGit/Roo-Cline/labels/codex
     

5. AI-assisted relabeling:

   • After migration, use AI to identify any mislabeled PRs or issues
   • Automatically suggest appropriate replacements
   • Script example:

     # Find PRs with issue/ labels and suggest pr/ equivalents
     gh pr list --repo RooVetGit/Roo-Cline --json number,labels | \
       jq '.[] | select(.labels[].name | startswith("issue/"))' | \
       # Process with AI to suggest appropriate pr/ labels
     

6. Verification:

   • Confirm all labels have been properly renamed or created
   • Verify that no unprefixed labels remain
   • Ensure consistent format across all labels

[KJ7LNW]

@hannesrudolph ^

[KJ7LNW]

Welcome @daniel-lxs !

@hannesrudolph asked me to put together the list above, perhaps this can be the beginning of some great standardization for tags that keep us organized.

[daniel-lxs]

@KJ7LNW This looks great, thank you!