GitHub - Classic Token (recommended)

How to integrate GitHub with Classic Token?

To connect GitHub to Hivel using a Personal Access Token (PAT), particularly with a service account to avoid integrating personal repositories, follow these steps:

Quick start: skip the navigation -open the token creation page, then continue from Step 4. If the link doesn't take you there, follow from Step 1 below.

Steps to be followed

Step 1: Prepare a Service Account

1. Log into the GitHub service account:

   • Use a dedicated service account that has access to the required repositories for Hivel integration.

   • Avoid using personal GitHub accounts to ensure only the intended repositories are accessed.

Step 2: Access Developer Settings

1. Click on the Profile Icon in the top-right corner of the GitHub dashboard.

2. Select Settings from the dropdown menu.

3. Scroll down and click on Developer Settings in the sidebar.

Step 3: Create a Personal Access Token

1. In Developer Settings, navigate to Personal Access Tokens.

2. Choose Tokens (classic).

Step 4: Configure the Classic Token

1. Click Generate New Token and select Classic Token.

2. Fill out the following details:

   • Token Name: Enter Hivel as the token name.

   • Expiration Date: Set it to no expiration date, or choose the longest period your organization's policy allows. (You can revoke this token manually when the engagement ends.)

3. Specify the scopes the token needs to operate effectively with Hivel:

   • repo (all)

   

   • admin:org (read:org)

   

   • User Select the following permissions:

     • Read:user

     • User:email

   
4. Once the configurations are complete, click Generate Token.

Step 5: Authorize the Token for SAML SSO Organizations (if applicable)

Additional step -only applies to organizations that have SAML SSO enabled; skip it otherwise.

1. If any of your organizations enforce SAML SSO, open the token under Personal access tokens → Tokens (classic).

2. Click Configure SSO next to the token, and Authorize it for each organization Hivel should access.

Without this, the token is valid but repositories in those organizations will not be visible to Hivel.

Step 6: Connect in Hivel

1. Copy the generated token immediately, as you won't be able to view it again.

2. Submit the token to Hivel.

Hivel validates the token instantly - if the token is wrong, expired, or missing any of the required scopes, Hivel shows a clear message telling you exactly what the problem is. Generate a new token with the correct scopes and reconnect.

That's it, all done!