From d370badeb51bdc1c54e5d4a7ca8ae67028428f32 Mon Sep 17 00:00:00 2001
From: Anna Danchenko <6584810+annadanchenko@users.noreply.github.com>
Date: Wed, 1 Nov 2017 08:33:29 +0100
Subject: [PATCH] Whitelist step is added

---
 doc/testing.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/testing.md b/doc/testing.md
index 26c4c33..421186c 100644
--- a/doc/testing.md
+++ b/doc/testing.md
@@ -35,7 +35,7 @@ Before you can create bounties, you need to have administrative access to one or
 * click on the button `Enable Github Account`
 * If you have 1 or more Organisation repositories then grant Organisation access to each of them by clicking on the button `Grant` 
 * grant Status Open Bounty the needed addtional permissions for managing repository webhooks, adding and modifying comments by clicking on the button `Authorize status-open-bounty`
-* now you should see your repositories on the `Repositories` tab, click `Add` on one. This should cause the `bounty` label to be available in the repository's labels and a new webhook should now exist for the repository.
+* now you should see your repositories on the `Repositories` tab, click `Add` on one. If your account isn't whitelisted you will see instructions how to request an access. If your account is whitelisted then new `bounty` label will become available in the GitHub repository's labels and a new webhook should now exist for the repository.
 * now, add the `bounty` label to a new or an existing issue. This should cause Status Open Bounty to post a new comment for the issue containing an image with text `Deploying contract, please wait`
 * once the contract has been mined, the comment will be updated to contain the bounty contract's address and a QR code