Skip to content

ci: add triage automation workflow#539

Closed
bdero wants to merge 1 commit intomainfrom
bdero/triage-automation
Closed

ci: add triage automation workflow#539
bdero wants to merge 1 commit intomainfrom
bdero/triage-automation

Conversation

@bdero
Copy link
Copy Markdown
Member

@bdero bdero commented May 2, 2026

Summary

Adds .github/workflows/triage.yaml to power the new weekly triage process.

PR-only flavor — only PRs are added to the queue (issues here aren't part of the meeting). On pull_request_target.opened it applies the needs-triage label so new PRs land in the org-level Triage project.

pull_request_target is used (not pull_request) so labeling works on PRs from forks. The workflow does not check out PR code, so it's safe.

Context

One of five PRs rolling out the new triage workflow across shorebird, _shorebird, dart-sdk, flutter, and docs. The label needs-triage was just created in this repo.

Test plan

  • Merge → open a test PR → confirm needs-triage is auto-applied

Adds a workflow that applies the new `needs-triage` label to PRs on
creation, so they show up in the org-level Triage project board.
@bdero
Copy link
Copy Markdown
Member Author

bdero commented May 2, 2026

Closing — we decided to drop PR labeling and rely on age-based saved views instead. See https://github.com/orgs/shorebirdtech/projects/25.

@bdero bdero closed this May 2, 2026
@bdero bdero deleted the bdero/triage-automation branch May 2, 2026 02:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant