Skip to content

[Code Quality] Standardize discussion category naming in workflows #13145

@github-actions

Description

@github-actions

Description

Workflow lock files create discussions with inconsistent category naming (capitalization and singular/plural forms), making it harder to search and organize automated reports.

Current State

Category naming inconsistencies found:

Inconsistent Count Should Be
Audits 6 audits
audit 1 audits
General 14 general
reports 3 reports
research 2 research

Total workflows creating discussions: 59 (40% of all workflows)

Issues

  1. Search Problems: Can't reliably search for all audit reports (need to check "audits", "Audits", "audit")
  2. Filtering Issues: GitHub Discussions filters treat these as separate categories
  3. Organization: Harder to group related reports together

Recommended Standard

Use lowercase, plural forms consistently:

  • audits - Security audits, workflow audits, analysis reports
  • general - General discussions and findings
  • reports - Various agent analysis reports (already consistent)
  • research - Research findings (already consistent)

Files Affected

Need to update workflows that create discussions with these categories:

  • "Audits" (6 workflows) - Change to audits
  • "audit" (1 workflow) - Change to audits
  • "General" (14 workflows) - Change to general

Likely location: Workflow frontmatter (.md files) in safe-outputs configuration or discussion category field.

Success Criteria

  • All 59 discussion-creating workflows use lowercase category names
  • Categories use plural form (audits not audit)
  • Documentation updated with category naming standard
  • Existing discussions optionally re-categorized (manual admin task)
  • Add validation to compiler to enforce lowercase categories

Implementation Plan

  1. Search workflow .md files for category: or create-discussion configurations
  2. Update category names to lowercase, plural forms
  3. Recompile affected workflows
  4. Add compiler validation to prevent future inconsistencies
  5. Document category naming standard in workflow authoring guide

Impact

  • Severity: Low (organizational issue, not functional)
  • Scope: 21 workflows with inconsistent categories
  • Benefit: Better searchability, cleaner organization, professional consistency

Source

Extracted from:

Priority: Low - Organizational improvement, no functional impact

AI generated by Discussion Task Miner - Code Quality Improvement Agent

  • expires on Feb 15, 2026, 5:09 PM UTC

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions