chore: remove reproduction link issue closing bot - #9034
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request removes the automated script, tests, and templates used for closing GitHub issues with invalid reproduction links. Feedback on the changes highlights that the workflow file .github/workflows/issues-no-repro.yaml itself was not deleted, which will lead to failing workflow runs since its underlying script has been removed.
| "" \ | ||
| "${PACKAGE_PATH}" \ | ||
| "samples",".github/workflows/ci.yaml,.github/workflows/issues-no-repro.yaml,.github/workflows/response.yaml,SECURITY.md,renovate.json" \ | ||
| "samples",".github/workflows/ci.yaml,.github/workflows/response.yaml,SECURITY.md,renovate.json" \ |
There was a problem hiding this comment.
It looks like .github/workflows/issues-no-repro.yaml is removed from the migration script list, but the workflow file itself is not deleted in this pull request. Since the underlying script .github/scripts/close-invalid-link.cjs has been deleted, any execution of this workflow will fail. Please delete .github/workflows/issues-no-repro.yaml as part of this PR to prevent failing workflow runs.
1 participant
This bot adds friction to file issues; at this point I believe its better to allow more issues and have a human decide if they are actionable or not, now that we can triage with AI agent support.