What do you need to successfully generate a support bundle on a GitHub Enterprise Server?

Question

Options

• AApproval from GitHub Support
• BA custom GitHub Action in the root repo
• CAdministrator SSH access to the appliance
• DA GitHub App with read:org permissions

• A
  2% (1)
• B
  2% (1)
• C
  95% (39)

Explanation

Administrator SSH access to the appliance (C) is required because generating a support bundle on GitHub Enterprise Server is an administrative operation performed via the command line - specifically using the ghe-support-bundle utility, which is only accessible through SSH as an admin user.

Why the distractors are wrong:

• A - GitHub Support approval is not a prerequisite; you generate the bundle yourself and then send it to support if needed.
• B - GitHub Actions is an automation platform; it plays no role in the appliance-level diagnostic tooling.
• D - A GitHub App with read:org permissions operates at the API level and has no access to the underlying server infrastructure needed to collect system logs and diagnostics.

Memory tip: Think of a support bundle as a server-level operation, not an API-level one. Any time you need to reach into the appliance's internals (logs, diagnostics, configuration), that requires SSH admin access - just like managing any Linux-based server.

No community discussion yet for this question.