From 9fa08750c0eea24a5dad89890ac561ee388f9944 Mon Sep 17 00:00:00 2001
From: Dan Abramov <dan.abramov@gmail.com>
Date: Thu, 7 Dec 2017 12:03:45 +0000
Subject: [PATCH] Mention how to use debuggers

---
 .github/PULL_REQUEST_TEMPLATE.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 3e93a2c8988b6..5429e507999cc 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -5,6 +5,7 @@
 3. If you've fixed a bug or added code that should be tested, add tests!
 4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development.
 5. Run `yarn test-prod` to test in the production environment. It supports the same options as `yarn test`.
+6. If you need a debugger, run `yarn debug-test --watch TestName`, open `chrome://inspect`, and press "Inspect".
 6. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`).
 7. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files.
 8. Run the [Flow](https://flowtype.org/) typechecks (`yarn flow`).