Update the text input triage process to route to platform teams#185225
Update the text input triage process to route to platform teams#185225loic-sharma wants to merge 1 commit intoflutter:masterfrom
Conversation
There was a problem hiding this comment.
Code Review
This pull request updates the triage documentation in docs/triage/README.md by adding instructions for using team-specific labels to manage pull request review queues. Feedback suggests extending this guidance to the incoming issue list to ensure consistent routing for platform-specific issues.
|
|
||
| - [P0 list](https://github.com/flutter/flutter/issues?q=is%3Aissue%20is%3Aopen%20label%3A%22a%3A%20text%20input%22%2C%22f%3A%20selection%22%2Cteam-text-input%2Cfyi-text-input%20sort%3Aupdated-asc%20label%3AP0) | ||
| - [PR list](https://github.com/flutter/flutter/pulls?q=is%3Aopen+is%3Apr+sort%3Acreated-desc+draft%3Afalse+label%3A%22a%3A+text+input%22%2C%22f%3A+selection%22%2Cteam-text-input%2Cfyi-text-input) | ||
| - Make sure that any PR that still needs review by a platform team has the appropriate `team-<platform>` label(s) on it, so that it shows up in the regular platform team triages. Once reviewed, the platform team can add the `triaged-<platform>` label to remove the PR from their triage queue. |
There was a problem hiding this comment.
This instruction is currently nested under the PR list, but the triage process for routing to platform teams likely applies to issues as well. Consider whether this guidance should also be added to the Incoming issue list (line 313) to ensure that platform-specific issues are correctly routed using team-<platform> labels.
Renzo-Olivares
left a comment
There was a problem hiding this comment.
LGTM thank you for updating this!
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
If this change needs to override an active code freeze, provide a comment explaining why. The code freeze workflow can be overridden by code reviewers. See pinned issues for any active code freezes with guidance.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.