anchor.diff:  - anchor:Whitelist[]Whitelist: If you choose not to whitelist entire organizations (see the link:#Organization[Organization] section), 
   you have the option to whitelist teams or users. Those who are whitelisted will not require approval to run the job against their PR.
   
  -image:github-pull-request-builder-sample-job3.png[Build Triggers Contd]
  +image:images/github-pull-request-builder-sample-job3.png[Build Triggers Contd]
   
   - anchor:Organization[]Whitelist Organizations: Check this if you want everyone in the listed organizations
   to be automatically approved, which will trigger the job when the PR is opened.
  
positive.code: Once you have a few jobs configured to check your PR's, and you have run some of them, you will see something like this image
  below on your PR:
  
  image:github-pull-request-builder-sample-job4.png[Build Triggers Contd]
  
  Now you have a better understanding of the impact of your PR, and can keep breaking updates out of your parent branches until you're ready!
negative.code: 
  #### Configuring a sample job
  
  image:images/github-pull-request-builder-sample-job1.png[SCM]
  
  NOTE: You will need to configure the *Source Code Management* section of your job specifically for the plugin. 
  Note in the image above, the *Name*, *Refspec*, and *Branch Specifier* sections - these ensure the plugin can view changes in PR's
  and the job runs against the correct commit hash. You will need to click the *Advanced* button to view some of the above fields.
  
  
  image:images/github-pull-request-builder-sample-job2.png[Build Triggers]
  
  NOTE: You will need to select the *Advanced* and *Trigger Setup* buttons to view all of the fields shown above. Here's an explanation
  of the available options:
  