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
{{ message }}
Repository navigation
Add option to use Github Enterprise API for api key checks #110
Migrated from augurlabs/augur#3277
Originally opened by @MoralCode on 2025-09-17
Augur is difficult to use for people using github's enterprise api (api.SUBDOMAIN.ghe.com) because keyman seems to validate credentials with a hardcoded API path.
Reactions are currently unavailable
Activity
collectoss-issue-migrator commented on Apr 30, 2026
Migrated comment from original
Originally posted by @SuyashJain17 on 2026-01-16
This looks like a well-scoped blocker for GitHub Enterprise users.
I’m going to trace where API key validation happens (keyman / auth flow) and see how the GitHub API base URL is currently hardcoded. I’ll aim for a minimal change that makes the API domain configurable while keeping api.github.com as the default. I’ll follow up with a proposal or PR once I understand the current flow.
Activity
collectoss-issue-migrator commentedon Apr 30, 2026
Note
Migrated comment from original
Originally posted by
@Ulincsyson 2025-09-17Related: #71
collectoss-issue-migrator commentedon Apr 30, 2026
Note
Migrated comment from original
Originally posted by
@SuyashJain17on 2026-01-16This looks like a well-scoped blocker for GitHub Enterprise users.
I’m going to trace where API key validation happens (keyman / auth flow) and see how the GitHub API base URL is currently hardcoded. I’ll aim for a minimal change that makes the API domain configurable while keeping api.github.com as the default. I’ll follow up with a proposal or PR once I understand the current flow.
MoralCode commentedon Jul 9, 2026
If anyone has access to a github enterprise instance that they could use to help test this functionality, that would be great