Replacing WIP in PR title with Drafts GitHub feature (#46292)

.github/CONTRIBUTING.md

@@ -121,6 +121,9 @@ For further details about commit message guidelines please visit:
         # gets changes from "master" branch on the "upstream" remote
 
  * Note: If this gives you an error, it means you have committed directly to your local `master` branch. [Click here for instructions on how to fix this issue](#why-does-git-pull---ff-only-result-in-an-error).
+
+         $ git push origin master
+         # optionally, push the synced master state to your fork
 
 #### Make your changes
 
@@ -143,12 +146,23 @@ For further details about commit message guidelines please visit:
 
  * Note: any new commits to the `new_feature` branch on GitHub will automatically be included in the pull request, so make sure to only commit related changes to the same branch.
 
-## Pull Request Notes
-If you file a PR but you're still working on it, please add a [WIP] before the title text. This will tell the reviewers that you still intend to add more to the PR and we don't need to review it yet. When it's ready to be reviewed by a merger just edit the title text to remove the [WIP].
+## Drafts
+If you file a PR but you're still working on it, please make it a [Draft](https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork).
 
-If you are also looking for suggestions then mark it with [CR] — "comments requested". You can use both [WIP] and [CR] to indicated that you need opinion/code review/suggestions to continue working (e.g. "[WIP] [CR] Super awesome big feature"). Feel free to remove [CR] when you feel you got enough information to proceed.
+![screenshot](https://docs.github.com/assets/images/help/pull_requests/pullrequest-send.png)
 
-This can help speed up our review process by allowing us to only review the things that are ready for it, and will prevent anything that isn't completely ready from being merged in.
+This will tell the reviewers that you still intend to add more to the PR and we don't need to review it yet. When it's ready to be reviewed for a merger, just click the [`Ready for review`](https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request) button.
+
+![screenshot](https://docs.github.com/assets/images/help/pull_requests/ready-for-review-button.png)
+
+Please convert all your existing PRs with `[WIP]` in the title to Drafts.
+
+![screenshot](https://docs.github.com/assets/images/help/pull_requests/convert-to-draft-link.png)
+
+This can help speed up our review process by allowing us to only review the things that are ready for it, and will help prevent merging in anything that isn't completely ready.
+
+## Comment requests
+If you are also looking for suggestions then add a [CR] before the title text — "comments requested". Feel free to remove [CR] when you feel you got enough information to proceed.
 
 It is not required to solve or reference an open issue to file a PR, however, if you do so, you need to explain the problem your PR is solving in full detail.
 
@@ -182,6 +196,10 @@ The "???" is the issue number. This automatically closes the issue when the PR i
 
 See https://help.github.com/articles/closing-issues-using-keywords/ for more.
 
+## Keep you PR description relevant
+
+Make sure your PR description is still relevant every time you change your branch after discussion or additional thought.
+
 ## Tooling support
 
 Various tools are available to help you keep your contributions conforming to the appropriate style.  See [the relevant docs](../doc/DEVELOPER_TOOLING.md) for more details.