Questions? We are here to help!

Connect GitHub to HEDESU

Connect GitHub so your team can work with GitHub issues from HEDESU tickets. Setup has two parts: install the HEDESU GitHub App for the organization, then choose the repositories available to your HEDESU tenant.

Before you begin

Use a HEDESU workspace administrator account. Having the Admin or Manager role in a space does not, by itself, grant access to GitHub setup; workspace-administrator access is assigned separately.

Coordinate installation and repository access with the person responsible for your GitHub organization. Confirm which organization and repositories your team needs.

Open GitHub setup

  1. In HEDESU, open Settings > Integrations.
  2. Find External Issue and the GitHub Setup section.
  3. Check the connection status and account. If the expected organization already has the HEDESU GitHub App installed, continue with repository selection.

Install the HEDESU GitHub App

  1. Select Install GitHub App when installation is needed and the control is available.
  2. Follow GitHub’s official installation instructions for the intended organization. Review the requested permissions and repository access. If approval is required, involve your organization owner and wait for that approval before continuing.
  3. Return to HEDESU and check that the expected organization is shown as Connected.

Use the installation entry point provided by HEDESU. The current setup does not ask you to create your own GitHub App or paste a client secret or private key into this page.

Choose tenant repositories

  1. Select Choose Tenant Repositories.
  2. Sign in with GitHub when prompted. HEDESU's setup page states that GitHub sign-in is required each time you open the console.
  3. Select the Organization. Under Allowed Repositories, select the repositories this tenant should use. The list is limited to repositories available both to the installation and your GitHub account.
  4. Select Save Repositories. Recheck the saved selection before configuring the relevant space's External Issue settings.

Installation access, tenant selection and space configuration are separate prerequisites. A Connected status alone does not establish that a particular space can create issues in every repository.

If setup is incomplete

If the console says GitHub sign-in required or Unable to link GitHub account, retry the sign-in flow; a profile-linked account alone does not unlock repository management. If the expected repository is unavailable, have your administrator check GitHub installation access, the signed-in GitHub account, tenant selection and the space configuration. If the connection is missing or belongs to the wrong organization, stop and have the integration administrator review it before creating issues.