DEVELOP-2270 Get code working for github enterprise#43
Merged
Conversation
jemmyw
approved these changes
Dec 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds some new settings so that we can utilize a Github Enterprise account for authorization.
We will need to still support the regular GitHub setup.
When supporting GitHub Enterprise, customers will need to create an OAuth application similar to what Aha! requires for the roadmap integration. Once created, they will need to provide us with the client ID and secret, along with their URL if it is not a cloud based enterprise account.
Then the only major differences are that we need to use
api/graphqlas the part instead of/graphqlwith theapisubdomain, and we will need to update how we verify valid pull requests.