Feat: Automatic SIG Inference from Test Names

[knabben]

Description

Currently, signalhound generates issue templates with a placeholder for SIG (/sig {{.Sig}}), but requires manual SIG assignment. The Release Signal handbook requires automatic SIG inference from test names to speed up issue triage.

Requirements

• Automatically extract SIG from test names using pattern [sig-*] (e.g., [sig-node] → SIG Node)
• For unit/verify test failures, infer SIG from OWNERS files or test path
• Integrate with Triage dashboard SIG inference when available
• Auto-populate SIG field in issue templates
• Support SIG inference in Slack messages and GitHub issue creation

Acceptance Criteria

• SIG is automatically detected from test names containing [sig-*] pattern
• SIG is inferred from OWNERS files for unit/verify tests
• SIG field is populated in all generated issue templates
• SIG is included in Slack message formatting
• Fallback to manual SIG selection if inference fails
• Unit tests for SIG inference logic
• Integration tests with real test names

Implementation Notes

• Pattern: \[sig-(\w+)\] regex extraction
• Check Triage API for SIG inference hints
• Map test paths to OWNERS files in k/k repository
• Default to empty SIG if inference fails (manual assignment)

[charliecheng630]

Hi @knabben , I would like to volunteer for this issue. After studying the codebase, here is my proposed implementation plan:

1. Data Model Layer
internal/testgrid/testgrid.go:Update the Test struct to include a SIG string field.

2. Core Inference Logic
internal/testgrid/inference.go (New File):

• Create a function (e.g. InferSIGFromTestName(name string)) to extract the SIG from explicit [sig-*] annotations in test names.
• Create a mapping function that takes a test file path and returns a SIG based on the k/k directory structure (e.g., pkg/volume -> storage).

internal/testgrid/testgrid.go:Integrate the inference functions into the HTML parsing loop so that every scraped test result is enriched with a SIG label.

3. TUI
internal/tui/issue.go:Pass the InferredSIG from the test data into the IssueTemplate struct used for rendering templates.

4. Testing

• pattern extraction
• Path-based inference
• OWNERS file parsing
• Integration tests with real test names from TestGrid

Is this direction aligned with your expectations? Any feedback on missing components would be appreciated.

[knabben]

@charliecheng630 the directions are looking good, you can assign the issue for yourself. I will keep an eye in the PR for review when it's time!

[charliecheng630]

/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale