Data Access by Hivel
- Hivel accesses the past 60 days of commits and pull requests from active repositories during the initial sync.
- Hivel employs GitHub's OAuth for authentication.
- Users maintain full control and can withdraw access anytime via GitHub's authorized apps section.
- 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.
- 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
- If logged into GitHub, log out.
- Log into the desired GitHub account for Hivel registration.
- Navigate to the Hivel sign-up page and click the GitHub logo.
- Authorize Hivel on the ensuing GitHub redirect.
- Click "Grant" for desired workspaces.
- After authorization, you'll be redirected back to Hivel.
- Fill in your organization details.
- Complete the process, and you'll be logged into Hivel.
- 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 firstname.lastname@example.org.
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.
Below are step-by-step screenshots of instructions you can refer to if needed.