Summary: 

Creating a pipeline via Github, either org folder or a single MBP, does not correctly setup webhooks. 

To reproduce: 

• Create a github token with correct scope allowing for admin of webhooks
• Create a MBP with the github project type, using this credential
• Note that there is no webhook created on the github project. 
• You will see a message in the log like: 

  INFO: GitHub webhooks activated for job CodeValet with [] (events: [REPOSITORY])

This also happens if you set it up via github org folders. rtyler swears on his grave that it used to work (he used it on jenkins.io) so this is possibly a bad regression. 

---------

See the attached screenshot, I haven't yet been able to figure out why sometimes, but mostly not, a webhook is created at an Org level.

*Most* of the time this doesn't work, but sometimes it does. MUCH CONFUSION.

Failed logs:

Aug 23, 2017 5:45:23 AM org.jenkinsci.plugins.github.webhook.WebhookManager$1 run              
INFO: GitHub webhooks activated for job CodeValet with [] (events: [REPOSITORY])   

Successful logs:

INFO: GitHub webhooks activated for job CodeValet with [] (events: [REPOSITORY])                          
Aug 23, 2017 5:41:04 AM org.jenkinsci.plugins.github_branch_source.GitHubOrgWebHook register              
INFO: A webhook was registered for the organization https://github.com/CodeValet                                                                                                                  
Aug 23, 2017 5:41:05 AM org.jenkinsci.plugins.github.webhook.subscriber.PingGHEventSubscriber onEvent                                                                                             
INFO: PING webhook received from org <https://api.github.com/orgs/CodeValet>!   

Related-ish to JENKINS-46365