Fix the contributing doc to be more direct about how contributions ar…

…e accepted.

PiperOrigin-RevId: 268465038

CONTRIBUTING.md

@@ -38,6 +38,12 @@ Please peruse Flutter's
 working on anything non-trivial. These guidelines are intended to
 keep the code consistent and avoid common pitfalls.
 
+You must complete the
+[Contributor License Agreement](https://cla.developers.google.com/clas). You can
+do this online, and it only takes a minute. If you've never submitted code
+before, you must add your (or your organization's) name and contact info to the
+[AUTHORS](AUTHORS) file.
+
 To start working on a patch:
 
  * `git fetch upstream`
@@ -54,14 +60,11 @@ To send us a pull request:
 
 Please make sure all your checkins have detailed commit messages explaining the patch.
 
-Once you've gotten an LGTM from a project maintainer and once your PR has received
-the green light from all our automated testing (Travis, Appveyor, etc), one of the
-project maintainers will merge the changes using a tool to sync with our internal
-flutter widgets repo. The PR will automatically be closed when the changes are
-merged externally.
+Once you've gotten an LGTM from a project maintainer and once your PR has
+received the green light from all our automated testing (Travis, Appveyor, etc),
+one of the project maintainers will merge the changes to our internal repo. This
+might cause test failures that need to be debugged internally so we might make
+further suggestions on your PR.
 
-You must complete the
-[Contributor License Agreement](https://cla.developers.google.com/clas).
-You can do this online, and it only takes a minute.
-If you've never submitted code before, you must add your (or your
-organization's) name and contact info to the [AUTHORS](AUTHORS) file.
+Once the internal change is submitted to the private repo, we will run our sync
+scripts to bring this repo up to date. At that point, your PR will be closed.