k8s-triage: allow "file bug" to target the repo under test instead of always kubernetes/kubernetes #37995

Currently the k8s-triage "file bug" button (https://storage.googleapis.com/k8s-triage/index.html) always files issues against kubernetes/kubernetes, even when the failing job belongs to a different repository (e.g. a periodic-cluster-api-* job). Maintainers of other SIG repos have to manually copy the generated issue text into their own repository.

Proposal

Use the existing "Repo" filter field to drive the target of the "file bug" action: when the field is populated with a well-structured repository value, the "file bug" button should file the issue in that repository instead of kubernetes/kubernetes.

This keeps the test-results URL unchanged (no breaking changes) and matches user expectation — someone filtering on a single repository would want the resulting issue created in that same repository.

Relevant code

• POST request construction: https://github.com/kubernetes/test-infra/blob/master/triage/interactive.js#L326
• Response rendering: https://github.com/kubernetes/test-infra/blob/master/triage/render.js#L324

Context / prior discussion

• Improve k8s-triage to be able to create issues in the Cluster API repo kubernetes-sigs/cluster-api#9851 (this request originated here)
• "Repo" field idea: Improve k8s-triage to be able to create issues in the Cluster API repo kubernetes-sigs/cluster-api#9851 (comment) (comment by @rexagod)
• Suggestion to file in test-infra: Improve k8s-triage to be able to create issues in the Cluster API repo kubernetes-sigs/cluster-api#9851 (comment) (comment by @sbueringer)

This issue was generated by AI, and reviewed by a human