How to handle /graphql vs. REST on Github Enterprise #6909
Replies: 2 comments 2 replies
-
Have you tried just setting the github url to https://my-github-enterprise-server.domain? You shouldn't have to append the api routes to the url, as that's handled by the request-making code. Whether or not the version of Enterprise Server you are running supports the v4 endpoint is a different matter altogether |
Beta Was this translation helpful? Give feedback.
-
Thank-you, I just reached a similar conclusion. https://my-github-enterprise-server.domain/api as the GITHUB_URL works great for the graphql badges, but not the rest ones, whereas https://my-github-enterprise-server.domain/api/v3, it's the reverse. We'll poke around with it. |
Beta Was this translation helpful? Give feedback.
-
I've found and successfully set my
GITHUB_URL
but have yet to figure out how to handle the fact that the REST API uses /api/v3 but the GRAPHQL doesn't. If I setGITHUB_URL
to https://myserver/api/v3, some end points like/github/last-commit/:user/:repo
work fine, but ones using /graphql, like/github/issues-pr/:user/:repo
fail because an invalid URL is constructed.Is there a configuration option to solve this?
Beta Was this translation helpful? Give feedback.
All reactions