Skip to main content
Skip to content

About GitHub Partner Support

Get help resolving issues for your customers with GitHub Partner Support. This paid, supplemental support program is available to select partners.

GitHub Partner Support lets partners open support tickets on behalf of their customers and escalate complex issues to GitHub Support. The partner remains the customer's primary point of contact.

Built on GitHub Enterprise Support, the offering includes accelerated initial response targets and priority case handling. Partner-specific workflows help you create, track, and manage customer support tickets.

GitHub Partner Support is available to select partners. To enroll, contact your Partner Development Manager.

Note

  • The terms of GitHub Partner Support ("Terms") are subject to change without notice and are effective as of November 16, 2026.
  • When you use GitHub Partner Support, the following terms apply: these Terms, the GitHub Services and Channel Partner Program Terms, the GitHub Services and Channel Partner Program Guide, and the terms of your Agreement (together, the "GitHub Partner Support Agreement"). By Agreement, we mean your main partner agreement with GitHub or Microsoft, for example, the GitHub Reseller and Distribution Terms.

What's included with GitHub Partner Support

The offering includes up to 50 customer support tickets using the Partner Support SLA per partner per subscription year, shared across the partner's customers. The subscription year starts on the date the partner purchases the offering. Tickets for the partner's own enterprise and customer tickets submitted with standard enterprise support do not count toward this allowance. See Service level agreement response times for the initial response targets.

The support request form shows your remaining ticket balance. Once the allowance is used up, you can still open customer tickets with standard enterprise support, but the Partner Support SLA does not apply.

GitHub partners can purchase GitHub Partner Support, which provides:

  • Written support, in English, through our support portal 24 hours per day, 7 days per week
  • Phone support via callback request, in English, through our support portal 24 hours per day, 7 days per week (when required to scope the issue)
  • Screen share request for critical issues
  • A Service Level Agreement (SLA) with guaranteed initial response times
  • Escalation management for High and Urgent priority tickets

Support Engineers have direct access to escalation engineering resources, if needed to expedite case resolution.

Scope of support

GitHub Support can help with issues related to GitHub's core features and functionality. For requests outside the scope of support, we may recommend other ways to resolve the issue.

For migrations, we support only GitHub-provided and documented tools. These include GitHub Enterprise Importer for migrations to GitHub Enterprise Cloud and ghe-migrator for migrations to GitHub Enterprise Server. GitHub Support can clarify documented tool behavior, but does not validate migration plans or assess overall migration readiness.

The following are outside the scope of support:

  • Migration planning, including repository inventories, sizing analysis, scoping, and prioritization
  • Git-only migrations, custom migration scripts, community migration tools, and third-party migration tools, which partners or customers must manage
  • CSP (Cloud Solution Provider) and CSP billing-related tickets are out of scope for this offering and would need to go through the existing CSP route
  • Third party integrations, e.g. Jira
  • Third-party continuous integration and continuous delivery tools, such as Jenkins
  • Azure DevOps (please contact Azure Support)
  • Writing scripts
  • Configuration of external authentication systems, e.g. SAML identity providers
  • Open source projects
  • Writing or debugging new queries for CodeQL
  • Cloud provider configurations, e.g. virtual network setup, custom firewall, or proxy rules
  • Container orchestration, e.g. Kubernetes setup, or networking
  • Detailed assistance with workflows and data management
  • Comprehensive support for customization and tool installation on GitHub Actions custom images
  • Preview features. Public preview, private preview, and technical preview features are out of GitHub Support's scope. Refer to GitHub's Sales team.
  • GitHub Copilot suggestions and outputs. For more information, see GitHub Terms for Additional Products and Features and Best practices for using GitHub Copilot.

For consulting, workshops, or training, partners with an active GitHub Partner Support subscription can purchase the GitHub Partner Success add-on. It provides 80 consulting hours per year with GitHub Expert Services, prorated for partial subscription terms. Partners can use these hours for services within the program's defined scope. For more information, see GitHub Partner Success Offering Terms.

If it's unclear whether the issue is out of scope, partners can open a ticket and GitHub Support will help determine the best way to proceed.

Setting up your GitHub Partner account

You must designate your global GitHub Enterprise Cloud enterprise account on GitHub.com as your partner enterprise. Use this account to grant support entitlements to your engineers. You cannot use a Data Residency tenant or a GitHub Enterprise Server instance as your partner enterprise.

Before opening tickets on behalf of a customer:

  1. Make sure each team member who needs to open tickets has a support entitlement in your own partner enterprise.

  2. Ask an enterprise owner at the customer's enterprise to approve your partner in their enterprise settings under Support. Only a customer enterprise owner can approve or remove a partner.

    • For customers with data residency, the owner manages approval on their GHE.com tenant.
    • For GitHub Enterprise Server customers, the owner manages approval through their existing global enterprise account on GitHub.com, not on the Server instance.

Partner users do not need membership or individual support entitlements in the customer's enterprise. Customer approval of the partner works across tenants. For more information, see Managing support entitlements for your enterprise.

Ticket complexity ownership

The following ticket complexities define the type of ticket handling and ownership between partners and GitHub Support:

OwnershipComplexityKey examples
Partner. Expected to handle all of these tickets for their customers.Scenarios that can be resolved using public documentation.Explaining product functionality with documentation. Using and configuring GitHub to resolve customer issues or errors.
GitHub. Work with partners to assist investigation.Errors and problems requiring system troubleshooting assistance not resolvable using documentation.Errors, problems; plus API rate-limits, Actions workflow issues, migration to GitHub. Server failure, organization-wide lockout, security exposure.

Ticket priority

For customer tickets using the Partner Support SLA, you answer questions about the issue's impact. GitHub Support uses that information to determine the ticket's priority. For more information, see About ticket priority.

PriorityExample impact
LowMinor issues, limited impact
NormalTypical issues, moderate impact
HighSignificant issues blocking activity for critical customers
UrgentSevere outages or critical customer impact, needs immediate attention

Service level agreement response times

The following initial response times apply to customer tickets using the Partner Support SLA and depend on the ticket's priority. The response time commences once GitHub Support defines the ticket priority. Tickets submitted with standard enterprise support do not receive the Partner Support SLA.

PriorityInitial response time
Urgent1 hour
High4 hours
Normal48 hours
Low48 hours

Contacting GitHub Support

To submit a support ticket on behalf of a customer:

  1. Complete the steps in Setting up your GitHub Partner account.
  2. Go to the GitHub Support portal and click Sign in with GitHub. Sign in with the GitHub.com account you use for your partner enterprise, including when submitting a ticket for a customer with data residency. See Creating a support ticket.
  3. At the top of the page, under "How can we help?", choose a topic or click Open a support ticket.
  4. In the Your Account field, select your own partner enterprise. This account validates your support entitlement and confirms you are an authorized partner.
  5. Under "For Support Partners", in Who is this ticket for?, select A customer enterprise.
  6. In the Customer Enterprise field, select the customer's enterprise. You will only see enterprises where an enterprise owner has approved your partner.
  7. Fill in the ticket details. See Information to include in your ticket.
  8. Review the remaining ticket balance shown with the support options. Choose Yes, apply GitHub Partner Support SLA to use a ticket from your allowance, or No, use standard enterprise support - no SLA. If you apply the Partner Support SLA, answer the questions about the issue's impact.
  9. Click Send request. Track updates in My tickets.

Information to include in your ticket

GitHub Support does not have access to private or internal GitHub resources. Include the information needed to understand, locate, and reproduce the issue to help reduce back-and-forth.

General requirements

In each ticket, include:

  • The affected enterprise, organization, or repository, including URLs and relevant usernames
  • A description of the issue, expected results, and exact error messages
  • Steps to reproduce the issue, if applicable
  • When the issue began, including the time zone
  • The impact on your customer's work and the number of affected users or repositories

Before sharing logs, screenshots, HAR files, or other diagnostics, review them for credentials and unrelated sensitive customer information. Redact that information before attaching the files. Do not include passwords, private keys, or full access tokens.

The following subsections list additional requirements for your issue and deployment.

GitHub Connect

For issues with GitHub Connect or its related features, include:

  • The name of the GitHub.com enterprise connected to your on-premises GitHub Enterprise Server instance

  • The exact error message when enabling GitHub Connect

  • Output from ghe-license info and chronyc sources -v (to check NTP synchronization) on the GitHub Enterprise Server instance

  • A support bundle from the GitHub Enterprise Server instance, which includes the information above

  • Details of the affected feature, if the issue is with a specific GitHub Connect feature

  • Output from these commands:

    curl -Iv https://github.com
    curl -Iv https://api.github.com
    curl -Iv https://uploads.github.com
    

For more information, see About GitHub Connect.

GitHub Enterprise Cloud and standalone GitHub Copilot

These requirements apply to GitHub Enterprise Cloud with or without Enterprise Managed Users, including enterprises with data residency, and standalone GitHub Copilot.

You need a support entitlement in your own partner enterprise, and an enterprise owner must approve your partner in the customer's enterprise. You do not need to be a member of the customer's enterprise.

Include the following information for the affected feature:

FeatureDetailsRequired information
Log requests(GHEC only) For security incidents (e.g. compromised personal access tokens (PATs), OAuth tokens, SSH keys, or accidental repository exposure) or requests for audit logs.Provide:
  • Add an organization owner to the ticket, as their consent is needed to share log events.
    • For logs related to PAT activity, consent must come from the owner of the affected token.
    • For logs related to a specific repository, consent should come from either the repository administrator or the organization owner.
Note: Audit logs are self-service and can be retrieved by customers directly.
Audit log streamingAudit log streaming functionalityProvide:
  • The enterprise name/URL where it's configured.
Enterprise account administrationAdministration of enterprise accountsProvide:
  • The enterprise name/URL.
  • A full browser screenshot of the configuration.
Organization and team administrationAdministration of orgs and teamsProvide:
  • The enterprise name/URL.
  • A full browser screenshot of the configuration.
IP allow listRestricting network traffic to your enterprise with an IP allow listProvide:
  • The partner should add an enterprise or organization owner to the ticket.
    • GitHub Support requires consent from the owner to disable IP Allow List and restore access.
    • If there are multiple owners, at least two should be included in the ticket, and consent is required from both.
    • Consent must come from the GitHub-verified email addresses of the owners.
SCIMOrg-level SCIM for non-EMU; Enterprise-level SCIM and team synchronization for EMU & ProximaProvide:
  • Team synchronization issues (e.g., a user not syncing with a team, or team sync itself isn't working):
    • The slug of the organization or enterprise where team sync is enabled.
    • The name of the team mapped to the IdP group.
    • The GitHub login name of the affected user(s).
    • A screenshot showing the user's presence in the mapped IdP group (from Entra or Okta).
GHEC DR (Proxima)For any issues related to data residency tenantsProvide:
  • The customer's tenant (e.g., xxxxx.ghe.com).
  • At least one enterprise owner should be included in the support ticket, along with a clear and concise description (and screenshot) of the issue.
API (v3:REST) & API (v4:GraphQL)Generic API endpoint/rate-limit issuesProvide:
  • For API rate limit issues:
    • Details on how the API call is made, including the affected user or app and the type of token used. Do not include the full token.
    • The request_id for the rate-limited call
    • The endpoint being called.
    • Verbose output
  • For general API endpoint issues, also include:
    • Information about the user or app making the request, plus the last 8 characters of the token
    • A screenshot of the error or the request_id
GitHub Applications (Apps and OAuth)Issues with appsProvide:
  • App ID/installation ID of the impacted app.
  • The request_id
  • For failing API calls:
    • The API query and its full output, with token information redacted.
WebhooksWebhook configuration and deliveryProvide:
  • Repository or organization URL where the webhook is configured.
  • The webhook URL and triggered event types.
  • Details of the issue (e.g., delivery failures, missing events, unexpected payloads).
  • Error messages or HTTP response codes.
  • Timestamps of affected webhook deliveries.
  • The delivery_id or request ID from webhook logs (if available).
  • Any recent changes to the webhook or related infrastructure.
  • Screenshots of the webhook configuration and any errors.
MigrationsAbout GitHub Enterprise ImporterProvide:
  • Migration logs
  • Source repository details (Vendor/repository size via git-sizer output)
GitHub CopilotGitHub Copilot functionality issues with the IDE.Provide:
  • Respective debug and network diagnostic logs.
  • Error details/screenshots.
Pull requests timeoutAngry Unicorn or 500 error accessing pull requests or repository components.Self-help:
  • Try in an incognito/private browsing window, or in another browser.
Provide:
  • Organization/repository details.
  • Reproduce the issue and capture a HAR file from the web browser's developer console.
Client connectivityIssue performing git operations from the local terminal to the remote GitHub. (example: git push/clone failures)Provide:
  • All output from https://github-debug.com
  • If using Git over HTTPS:
    • GIT_TRACE=1 GIT_CURL_VERBOSE=1 <git command>
  • If you're using Git over SSH:
    • GIT_TRACE_PACKET=1 GIT_TRACE=1 GIT_TRACE_PERFORMANCE=1 GIT_SSH_COMMAND="ssh -vvv" <git command>
GitHub Copilot models unavailableUser complaining about AI models unavailability after the GitHub Copilot seat assignmentSelf-help:
  • Ensure policies are configured appropriately.
Provide:
  • Screenshot of the user's IDE/UI.
Sensitive data removalRemoving sensitive data from a repositorySelf-help:
  • Ensure the end user has rewritten and pushed the cleaned history as described in Removing sensitive data from a repository before reaching out to GitHub Support.
  • Remove references to the sensitive commit from branches, tags, and forks. Ask GitHub Support to remove the remaining pull request references and cached views.

Authentication

Authentication issues include SAML, OIDC, and conditional access policies for Enterprise Managed Users using Entra.

For SAML lockout cases, such as SAML certificates with no recovery codes, add an enterprise or organization owner to the ticket, depending on where SAML SSO is configured:

  • GitHub Support requires consent from the owner to disable SAML SSO and restore access.
  • If there are multiple owners, include at least two in the ticket. Consent is required from both.
  • Consent must come from the owners' GitHub-verified email addresses.

GitHub Actions workflow runs

For workflow failures and self-hosted runner issues, first capture the unexpected behavior:

  1. Enable debug logging. See Enabling debug logging.
  2. Run the workflow to reproduce the issue.

Include these details and attachments in your ticket:

  • The URL of the workflow run with debug logging enabled, for example: https://github.com/ORG/REPO/actions/runs/0123456789
  • Copies of the complete workflow .yml files as attachments. You may need to change the extension to .txt to attach them. See Workflows.
  • Workflow run logs for an example failure with debug logging enabled, attached to the ticket. See Using workflow run logs.
  • For self-hosted runners, logs from the runner's _diag folder as attachments. The filenames use the formats Runner_YYYY####-xxxxxx-utc.log and Worker_YYYY####-xxxxxx-utc.log. See Monitoring and troubleshooting self-hosted runners.
  • If you use Actions Runner Controller (ARC), logs for the controller and runner set listeners. See Troubleshooting Actions Runner Controller errors.

CodeQL results and code scanning alerts

For unexpected analysis results or alert states, include:

If you run CodeQL through GitHub Actions, enable debugging artifacts and attach them to your ticket as a .zip file. See Logs are not detailed enough.

If you run CodeQL with the CLI, retrieve the SARIF file from the database analyze command output.

GitHub Enterprise Server

Include the following information about the customer's instance:

  • A support bundle or diagnostic report from the customer's on-premises GitHub Enterprise Server instance
  • Relevant screenshots or recordings
  • For issues related to high availability replication, provide the output of ghe-repl-status from the problematic replica GitHub Enterprise Server instance.
  • Confirmation of any changes to the appliance, such as version upgrades, network modifications, or other configuration updates that could affect functionality
  • For licensing questions, provide the output of ghe-license info so we can identify the license or subscription linked to the customer's instance.

Resolving and closing support tickets

GitHub Support may consider a ticket solved after providing an explanation, recommendation, usage instructions, workaround instructions, or by advising you of an available GitHub Enterprise Server release that addresses the issue.

If you use a custom or unsupported plug-in, module, or custom code, GitHub Support may ask you to remove the unsupported plug-in, module, or code while attempting to resolve the issue. If the problem is fixed when the unsupported plug-in, module, or custom code is removed, GitHub Support may consider the ticket solved.

GitHub Support may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered.

Callback requests

Callback requests should only be used when a live discussion is essential to scope the issue.

When requested, the assigned Support Engineer will determine whether a phone call or Zoom/Teams meeting with screen sharing is the most efficient way to move the ticket forward.

Callback requests are not tied to SLAs. A Support Engineer or representative will respond as soon as possible based on ticket priority and availability.

Our live support calls focus on gathering essential information and aligning expectations. Once these goals are met, our Support Engineers end the call to focus on resolving your issue as quickly as possible.

Termination

Your GitHub Partner Support Agreement will automatically end if your membership in the GitHub Services and Channel Partner Program is terminated. Please note that fees paid for GitHub Partner Support are non-refundable if you terminate your membership without cause, or if GitHub terminates your membership for cause.