chore: cut over GitHub Actions from Triage board to App project board - #34370
chore: cut over GitHub Actions from Triage board to App project board#34370cacieprins wants to merge 2 commits into
Conversation
- Delete triage_add_to_project, triage_add_to_routed_project, triage_handle_new_comments, triage_update_status (all Triage project 9 specific; board management moves to GitHub built-in auto-add on App project 10) - Add contributor_comment workflow: posts contributing guide comment on new external issues/PRs (extracted from triage_add_to_project) - Add close_waiting_for_reproduction workflow: daily auto-close for open issues in "Waiting for Reproduction" status with no activity for 2 days - Drop routed-to-* and triaged exempt labels from stale cleanup Co-authored-by: Cursor <cursoragent@cursor.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
…roduction - Add label_prevent_stale workflow: applies prevent-stale to issues opened by collaborators so they are exempt from the Waiting for Reproduction auto-close timeout - Fix close_waiting_for_reproduction to handle issues from any repo on the project board (use repository.nameWithOwner instead of hardcoded cypress repo) - Respect prevent-stale label: skip auto-close for exempt issues Co-authored-by: Cursor <cursoragent@cursor.com>
| script: | | ||
| const script = require('./scripts/triage/comment_workflow.js') | ||
| await script.handleComment(github, context); | ||
| const script = require('./scripts/triage/add_contributing_comment.js') |
There was a problem hiding this comment.
Where is this located? I don't see this in the repo.
There was a problem hiding this comment.
These are in the automations repo: https://github.com/cypress-io/release-automations/tree/master/scripts/triage/add_contributing_comment.js
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9b27213. Configure here.
| if (now - updatedAt > staleMs) { | ||
| const [owner, repo] = content.repository.nameWithOwner.split('/') | ||
| staleIssues.push({ number: content.number, title: content.title, owner, repo }) | ||
| } |
There was a problem hiding this comment.
Premature reproduction wait auto-close
High Severity
The stale check uses only the issue updatedAt, and project status changes do not update that timestamp. Moving an already-inactive issue into Waiting for Reproduction can make it eligible to close on the next cron run, even though it has not been waiting in that column for 2 days. The close comment would then incorrectly claim a 2-day wait.
Reviewed by Cursor Bugbot for commit 9b27213. Configure here.
3 participants
Summary
triage_add_to_project,triage_add_to_routed_project,triage_handle_new_comments,triage_update_status). Board auto-add moves to the GitHub Projects built-in auto-add workflow on App (project 10).contributor_commentworkflow (fires on new external issues/PRs).close_waiting_for_reproductionworkflow: daily cron that closes open issues sitting in Waiting for Reproduction on the App board with no activity for more than 2 days.routed-to-*andtriagedfrom stale cleanup exempt labels since those labels are no longer part of the new flow.Pre-merge checklist
ADD_TO_TRIAGE_BOARD_TOKENhasissues: writepermission (needed byclose_waiting_for_reproduction)Test plan
close_waiting_for_reproductionviaworkflow_dispatchand verify it pages through project items without error (no items will be closed if none are stale)Related
N/A
Changelog
N/A — internal CI/automation change only
Made with Cursor