GitHub-Alternate SignUp Method Instructions

Data Access by Hivel

• Hivel accesses the past 60-90 days of commits and pull requests from active repositories during the initial sync.

Authorization Mechanism

• Hivel employs GitHub's OAuth for authentication.

• Users maintain full control and can withdraw access anytime via GitHub's authorized apps section.

Requirements

• Utilize a service account with Read access to all GitHub repositories that developers engage with.

Real-time Data Synchronization

• A GitHub Access Token with Write access is necessary to deploy webhooks for real-time data. This token should have a 2-day expiration.

• The token enables webhook deployment to current repositories. For repositories created in the future, we advise admins to either:

  • Manually append the webhooks.

  • Develop a basic script to auto-append webhooks to new repositories.

Best Practice

• Opt for a service account rather than an individual-linked account.

• Service accounts are typically overseen by the company's admin.

How to Connect Your GitHub Account to Hivel

1. If logged into GitHub, log out.

2. Log into the desired GitHub account for Hivel registration.

3. Navigate to the Hivel sign-up page and click the GitHub logo.

4. Authorize Hivel on the ensuing GitHub redirect.

5. Click "Grant" for desired workspaces.

6. After authorization, you'll be redirected back to Hivel.

7. Fill in your organization details.

8. Complete the process, and you'll be logged into Hivel.

9. For real-time data synchronization, as mentioned in the section above, create a Personal Access Token which has write permission to publish webhooks to your repositories, and share it with the Hivel Team or to [e-mail].

At Hivel, your security is not just a priority—it's a commitment. We employ robust measures to safeguard your data and protect your privacy. Learn More.