Skip to main content

GitHub connector settings reference

This topic provides settings and permissions for the GitHub connector. For instructions and more information about code repo connectors, go to Connect to a Git repository.

Overview settings​

  • Name: The unique name for this connector. Harness generates an Id (Entity Identifier) based on the Name. You can edit the Id during initial connector creation. Once you save the connector, the Id is locked.
  • Description: Optional text string.
  • Tags: Optional labels you can use for filtering. For details, go to the Tags reference.

Details settings​

The Details settings specify which GitHub account or repository you want this connector to connect to, whether to connect over HTTP or SSH, and the URL to use.

URL Type​

Select Account to connect an entire GitHub account (or organization). This option lets you use one connector to connect to all repositories in the specified GitHub account. Make sure you have at least one repo in the account; you need a repo to test the connection and save the connector.

Select Repository to connect to a single, specific GitHub repository.

Connection Type​

Select the protocol, HTTP or SSH, to use for cloning and authentication. The Connection Type determines the URL format required for the GitHub Account/Repository URL field. It also determines the Authentication method you must use in the Credentials settings.

GitHub Account/Repository URL​

Enter the URL for the GitHub account or repository that you want to connect to. The required value is determined by the URL Type and Connection Type.

In the GitHub Account URL field, provide only the account-identifying portion of the GitHub URL, such as https://github.com/YOUR_ACCOUNT_NAME/. Do not include a repo name. The URL format depends on the Connection Type:

  • HTTP: https://github.com/YOUR_ACCOUNT_NAME/ or https://github.com
  • SSH: git@github.com:YOUR_ACCOUNT_NAME/

Test Repository​

This field is only required if the URL Type is Account. Provide the name of a repo in your GitHub account that Harness can use to test the connector. Harness uses this repo to validate the connection only. When you use this connector in a pipeline, you'll specify a true code repo in your pipeline configuration or at runtime.

GitHub Enterprise URLs

For Github Enterprise, the URL must include your hostname and the organization name, such as https://mygithub.com/harness/repo-name.git or git@mygithub.com:harness/repo-name.git. In these examples mygithub.com is the hostname and harness is the organization name.

Credentials settings​

Provide authentication credentials for the connector.

Authentication​

Authentication is required for all accounts and repos, including read-only repos. The Connection Type you chose in the Details settings determines the available Authentication methods:

  • For HTTP connections, you can use Username and Token, OAuth, or GitHub App authentication.
  • For SSH connections, you must use SSH Key authentication.
  1. For Authentication, select Username and Token.
  2. In the Username field, enter your personal GitHub account name. You can use either plaintext or a Harness encrypted text secret.
  3. In the Personal Access Token field, provide a GitHub personal access token as a Harness encrypted text secret.
Personal access token permissions
  • The GitHub user account that you use to create the token must have admin permissions on the repo.
  • For GitHub organizations that use SAML single sign-on (SSO), you must authorize the token for use with SAML single sign-on.
  • The token must have all repo, user, and admin:repo_hook scopes. GitHub doesn't provide a way to scope tokens for read-only access to repos.

GitHub token permission scopes.

tip

You can validate your token from the command line before using it in Harness. For example:

curl -i https://api.github.com -u <username>:<token>

Enable API access​

This setting is only available for connection types and authentication methods where it is not already enabled by default.

API access is required for any operations that require Harness to call GitHub APIs, such as using the Harness Git Experience, cloning codebases, automatically detecting branch names when you manually run pipelines, using Git webhook triggers, and updating Git statuses.

Enabling API access requires configuring an API authentication method, either a personal access token or a GitHub App.

  1. For API Authentication, select Personal Access Token.

  2. In the Personal Access Token field, provide a GitHub personal access token as a Harness encrypted text secret.

    If you are using Username and Token authentication, use the same personal access token secret for both Personal Access Token fields.

Personal access token permissions
  • The GitHub user account that you use to create the token must have admin permissions on the repo.
  • For GitHub organizations that use SAML single sign-on (SSO), you must authorize the token for use with SAML single sign-on.
  • The token must have all repo, user, and admin:repo_hook scopes. GitHub doesn't provide a way to scope tokens for read-only access to repos.

GitHub token permission scopes.

Connectivity Mode settings​

Select whether you want Harness to connect directly to your GitHub account or repo, or if you want Harness to communicate with your GitHub account or repo through a delegate. If you plan to use this connector with Harness Cloud build infrastructure, you must select Connect through Harness Platform.

About connectivity modes

If you select Connect through the Harness Platform, the Harness Manager exchanges a key pair with the Secrets Manager configured in Harness using an encrypted connection. Next, the Harness Manager uses the encrypted key and the encrypted secret and then discards them. The keys never leave the Harness Manager. Secrets are always encrypted in transit, in memory, and in the Harness database.

Connect through a Harness Delegate, a Harness delegate handles the connection. This option is often used for Harness Self-Managed Enterprise Edition Overview.

Delegates Setup​

If you select Connect through a Harness Delegate, you can select Use any available Delegate or Only use Delegates with all of the following tags.

If you want to use specific delegates, you must identify those delegates. For more information, go to Use delegate selectors.

Kubernetes delegate with self-signed certificates​

If your codebase connector allows API access and connects through a Harness Delegate that uses self-signed certificates, you must specify ADDITIONAL_CERTS_PATH in the delegate pod, as described in Configure a Kubernetes build farm to use self-signed certificates.