You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the way we determine the code forge is by matching the remote URL.
For GitHub, it must be github.com, or whatever is configured with GITHUB_URL.
Per discussion in #330, a better UX for GHES would be the ability to specify that they're using a specific kind of forge (e.g. GHES), and then the GitHub URL is determined based on the Git remote, and the API URL guessed based on that.
The text was updated successfully, but these errors were encountered:
For GHES, usually the API URL is /api under the base URL.
So if the API URL is not set, and base URL is not github.com,
we can assume the API URL is $baseURL/api.
Users can still override this with the `spice.forge.github.apiUrl`
or `GITHUB_API_URL` environment variable.
Follow up to
#330 (comment)
Relates to #336
Right now, the way we determine the code forge is by matching the remote URL.
For GitHub, it must be github.com, or whatever is configured with GITHUB_URL.
Per discussion in #330, a better UX for GHES would be the ability to specify that they're using a specific kind of forge (e.g. GHES), and then the GitHub URL is determined based on the Git remote, and the API URL guessed based on that.
The text was updated successfully, but these errors were encountered: