From 0783aa7debc6720306e7f345e5beace07febba64 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20Freitag?= Date: Mon, 21 Nov 2016 03:55:03 -0800 Subject: [PATCH] Refs #23811 -- Corrected git bisect run example usage. --- docs/internals/contributing/triaging-tickets.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/internals/contributing/triaging-tickets.txt b/docs/internals/contributing/triaging-tickets.txt index c121e86b26..bad14dd54c 100644 --- a/docs/internals/contributing/triaging-tickets.txt +++ b/docs/internals/contributing/triaging-tickets.txt @@ -460,7 +460,7 @@ find a revision where your test passes, mark it as "good":: Now we're ready for the fun part: using ``git bisect run`` to automate the rest of the process:: - $ git bisect run python runtests.py migrations.test_regression + $ git bisect run tests/runtests.py migrations.test_regression You should see ``git bisect`` use a binary search to automatically checkout revisions between the good and bad commits until it finds the first "bad"