- 
    
Improvement
 - 
    Resolution: Unresolved
 - 
    
Major
 
If I install this plugin, and attempt to use it with a GitHub Enterprise server (via New Item > Multibranch pipeline > Branch Sources > GitHub), there isn't any documentation.
I discovered that there is a "API endpoint" dropdown, but it just says "GitHub" and has no documentation.
If I go to Manage Jenkins > Manage System, I see two different places to configure GitHub servers — one comes from the GitHub plugin, which is a dependency. This is directly followed by a duplicate, but less-detailed configuration UI, provided by this plugin.
Ideally, there should be one single, documented place to enter the required information.
- is duplicated by
 - 
                    
JENKINS-39025 Pull request from forks are not build
-         
 - Resolved
 
 -         
 - 
                    
JENKINS-46366 REGRESSION: Github branch source does not consistently set up webhook
-         
 - Resolved
 
 -         
 - 
                    
JENKINS-42992 Webhooks don't work from GitHub Enterprise when using Multi-Branch Pipeline jobs
-         
 - Resolved
 
 -         
 - 
                    
JENKINS-37845 GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with
-         
 - Resolved
 
 -         
 
- is related to
 - 
                    
JENKINS-33318 GitHub Enterprise Server validation does not work when private mode is enabled
-         
 - Resolved
 
 -         
 - 
                    
JENKINS-41633 UX: non-obvious that API tokens need to be stored as UsernamePassword to work as scan credentials
-         
 - Open
 
 -         
 
- links to