3 ms·
You would just have to switch out https://api.github.com/ https://api.github.com/ with https://{Your https://{Your company's Github Enterprise location}/api/v3/
by dkroy 12y ago
You would just have to switch out https://api.github.com/ https://api.github.com/ with https://{Your https://{Your company's Github Enterprise location}/api/v3/
- yblu 12y agoDo you know if GitHub Enterprise imposes an API limit for unauthenticated requests? If it does, does it support personal access token? (See https://github.com/buunguyen/octotree#github-api-rate-limit. https://github.com/buunguyen/octotree#github-api-rate-limit.) Depending on the answers, it could be very simple change, i.e. allow users to configure API subdomain. Unfortunately, I don't have any GitHub Enterprise deployment in handy at this moment to find out.
- jansanchez 12y ago> If it does, does it support personal access token? Yes, it does support tokens.
- yblu 12y agoThanks for confirming. Then it should be straightforward to support. I'll hope to have access to a Enterprise deployment to test out.
- Myrmornis 12y agoI believe the Github developer program [1] gives you access to a github enterprise instance for exactly this purpose. [1] https://developer.github.com/program/ https://developer.github.com/program/
- gknoy 12y agoThank you! That's solved my immediate problem. Now to refactor so that we can dynamically determine the URL based on the current path...