Standardize review timeline guidance (#183465)

stuartmorgan-g · gemini-code-assist[bot] · web-flow · commit 00b5a48a86f2 · 2026-03-11T16:59:19.000Z
Currently on the same page we say to ping people:
- After two weeks (in When) (and the tl;dr).
- After one week (in Who).
- Immediately, in step 7 of the PR process overview.

This makes it hard for new contributors to understand what the actual
expectation is, and in practice the step 7 version creates behavior we
don't want (immediately pinging people, usually the wrong ones, instead
of waiting for the normal triage process).

This standardizes everything on two weeks.

---------

Co-authored-by: gemini-code-assist[bot] &lt;176961590+gemini-code-assist[bot]@users.noreply.github.com&gt;
diff --git a/docs/contributing/Tree-hygiene.md b/docs/contributing/Tree-hygiene.md
@@ -69,10 +69,9 @@ The general process for submitting code to a Flutter repository is as follows:
    This doesn’t prohibit the use of coding assistance tools, but what’s submitted does
    need to be a contributor’s original creation.
 
-7. Get your code reviewed (see below). You should probably reach out to the relevant
-   expert(s) for the areas you touched and ask them to review your PR directly.
-   GitHub sometimes recommends specific reviewers; if you're not sure who to ask,
-   that's probably a good place to start.
+7. Get your code reviewed (see below). If you are a team member, request review
+   from the relevant expert(s) for the areas you touched. Otherwise, wait for
+   [reviewers to be assigned](#who).
 
 8. Make sure your PR passes all the pre-commit tests. Consider running some of the
    post-commit tests locally (see the
@@ -245,12 +244,9 @@ Code should be reviewed by the owner (tech lead) of the area(s) of the codebase
 or someone to whom they have delegated that authority.
 If anyone else leaves comments, please also wait for their approval (LGTM) before landing code.
 
-If nobody has reviewed your code after a week, then reach out on our [Chat](Chat.md) channels.
+If nobody has reviewed your code after two weeks, then reach out on our [Chat](Chat.md) channels.
 The `#hackers-new` channel is a good place to ask for help if you're a new contributor.
 
-_For PRs affecting the `material` and `cupertino` libraries, team members are expected to seek reviewers directly;
-they will not be assigned during PR triage._
-
 ### How
 
 Code review status is managed via GitHub's approval system. PRs should
