e2e: updating PR pipeline

Author: churik

doc/pipeline_process.md

@@ -62,7 +62,8 @@ Please, respect this rule.**
 #### Prerequisites for manual testing
 1. PR has a description and the area affected.
 2. PR has automation results from the previous step.
-3. PR includes a demo, test steps, and possible regression.
+3. PR includes a demo, test steps, and possible regression
+4. PR has out of scope (if appropriate)
 
 **If one of the prerequisites is missing, the PR will be moved to the contributor folder with a corresponding comment.**
 
@@ -97,7 +98,7 @@ There are three possible scenarios when the design review is completed:
 ---        
 
 #### Why my PR is in `Contributor` column?
-PR can be moved to this column by the ```status-github-bot``` or by QA engineer with label `Tested-issues`.
+PR can be moved to this column by the ```status-github-bot``` or by QA engineer with label `Tested-issues` or if one of the requirement for manual QA was not met.
 In the first case most often this happens due to conflicting files in PR.
 In the second case - after fixing of all found issues, the developer should ping the QA in the PR comments for retesting.
 
@@ -115,7 +116,6 @@ In the second case - after fixing of all found issues, the developer should ping
 6. In case of manual testing - the label ```Tested - OK``` from QA
 7. In case of design review - the approval from the designer
 
-
 You can merge your PR into develop - some useful clues you can find [here](https://notes.status.im/setup-e2e#3-Merging-PR) 
 
 HAPPY DEVELOPMENT! :tada: