Skip to content

Add option to use Github Enterprise API for api key checks #110

Open

Description

@collectoss-issue-migrator

Note

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.

Activity

  1. collectoss-issue-migrator commented on Apr 30, 2026

    @collectoss-issue-migrator
    Author

    Note

    Migrated comment from original
    Originally posted by @Ulincsys on 2025-09-17


    Related: #71

  2. collectoss-issue-migrator commented on Apr 30, 2026

    @collectoss-issue-migrator
    Author

    Note

    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.

  3. MoralCode commented on Jul 9, 2026

    @MoralCode
    Contributor

    If anyone has access to a github enterprise instance that they could use to help test this functionality, that would be great

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions