Feat: Track Issues and PRs in Current Milestone

[knabben]

Description

The handbook requires tracking issues and PRs targeted for the current release cycle, detecting stale issues, and generating summary reports. Currently, signalhound does not track issue lifecycle or generate reports.

Requirements

• Track all issues and PRs in current milestone
• Detect stale issues (no updates in 3+ months)
• Generate automated follow-up comments on stale issues
• Integrate with Bug Triage Board
• Generate summary reports for release team meetings

Acceptance Criteria

• Issues and PRs in milestone are tracked
• Stale issues are detected (3+ months without updates)
• Automated follow-up comments are generated for stale issues
• Integration with Bug Triage Board
• Summary reports are generated (markdown format)
• Reports include counts by status, priority, SIG
• Unit tests for tracking logic
• Integration tests with GitHub API

Implementation Notes

• Query GitHub API for issues/PRs in milestone
• Track issue state changes over time
• Generate reports in markdown format
• Support --generate-report command
• Cache issue data to reduce API calls

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten