Skip to content

[AI Ops] Finalise the automated labeling infrastructure #32

@ashleyshaw

Description

@ashleyshaw

AI Ops Summary

  • Review logic for applying labels via branch, file, and content heuristics
  • Add or upgrade logging for traceability and debugging
  • Identify and fix bugs in automated label application, one-hot enforcement, and migration/removal of legacy labels

Problem Statement

The labeling infrastructure is currently in place but is broken due to bugs and missing logging. We need to:

  • Audit every instruction and code file related to labeling automation
  • Add/upgrade logging for better traceability
  • Debug and patch each issue
  • Validate the system end-to-end

Scope & Deliverables

  • Validate unified labeling agent and workflow (labeling.agent.js, labeling.yml)
  • Audit and debug canonical config files: labels.yml, labeler.yml, issue-types.yml
  • Review and patch automation governance and agent instructions
  • Verify minimum required label enforcement and migration logic
  • Add/upgrade logging throughout labeling workflows and agents
  • Document troubleshooting steps and root cause analysis for each bug
  • Ensure all documentation references are accurate and up-to-date

Success Criteria

  • All bugs in labeling automation are resolved
  • Comprehensive logging is added to all labeling agents and workflows
  • Labeling rules and enforcement are validated against configs
  • Documentation is accurate, cross-linked, and up-to-date
  • Maintainers and contributors can reliably use automation for labeling without manual intervention

References

  • Labeling Agent Spec
  • Labeling Agent Instructions
  • Labeling Workflow
  • Canonical Labels
  • Labeler Rules
  • Issue Types
  • Label Strategy Documentation
  • Automation Governance
  • Issue Labels Guide
  • PR Labels Guide

This epic will be broken down into sub-issues for each component (agent, workflow, configs, logging, governance, docs, and troubleshooting).

Acceptance Criteria

  • AI workflow/agent described
  • Problem/opportunity scoped
  • Success metric defined
  • Documentation updated
  • PR uses correct branch prefix (ai/)
  • Approved by at least one maintainer

Additional Context

References


Definition of Ready (DoR)

  • AI ops goal described
  • Area/action mapped
  • Acceptance criteria listed
  • Estimate added

Definition of Done (DoD)

  • All acceptance criteria met
  • Solution/automation verified
  • Documentation updated
  • PR uses correct branch prefix (ai/)

Metadata

Metadata

Type

Priority

None yet

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions