Global configuration provided for this plugin to handle GitHub Entreprise instances, IMO, it is enough.
Yeah... if the existing UI was good enough, then I wouldn't have filed this issue, and Cyrille Le Clerc wouldn't have submitted PR #25!
Firstly, someone seeing "API endpoint" as a configuration option won't magically know that this is supposed to be a URL pointing to the base path of the API on the GitHub Enteprise server. Even if they do enter a URL, they will probably see "This does not look like a GitHub Enterprise API URL".
What should they do when they see this? What should a GH Enterprise API URL look like? Again, there is zero inline documentation.
There are even three different code paths which show this same message at the moment — one of which is wrong, since if the GH Enterprise instance has anonymous access disabled, you'll get an IOException: "WARNING: Server returned HTTP response code: 401 for URL: https://github.example.de/api/v3/"
Anyway, aside from the fact that every config option should be clearly named and clearly documented, it misses the main point — the needless duplication.
As a user, I don't really care which dependency this plugin uses, so long as the UI is consistent. If relying on the github-plugin makes it more consistent, then great. If this plugin and the github-plugin both end up relying on some new github-library-ui plugin, also great. But right now, the duplication of UI here makes no sense.