Feat: Automatic Milestone Assignment and Management

[knabben]

Description

The Release Signal handbook requires all issues to be assigned to the current milestone using /milestone v1.x Prow command. Currently, signalhound does not support milestone management.

Requirements

• Detect current Kubernetes release milestone (e.g., v1.33)
• Automatically add /milestone v1.x command to issue bodies
• Support milestone migration at end of release cycle
• Integrate with milestone-maintainers team permissions
• Allow manual milestone override

Acceptance Criteria

• Current milestone is automatically detected from GitHub API or config
• /milestone v1.x command is added to all generated issue templates
• Milestone can be configured via environment variable or config file
• Support for milestone migration (move non-blocking issues to next milestone)
• Unit tests for milestone detection and assignment
• Integration tests with GitHub API

Implementation Notes

• Query GitHub API for active milestones in kubernetes/kubernetes
• Or read from config file/environment variable
• Add milestone command to issue template generation
• Support --milestone flag for manual override

[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