Skip to main content
A GitHub benefit turns product access into repository membership. Ruba invites a customer after entitlement begins and removes that access when the entitlement ends. It works with subscriptions and one-time products.

​
What you can deliver

  • Sponsor-only source, discussions, or issue access
  • Courses, starter kits, and educational repositories
  • Self-hosted software and open-core extensions
  • Early builds that are not yet available upstream
Create more than one benefit when a product needs to unlock several repositories or repositories from different organizations.

​
Connection model

This benefit uses a dedicated GitHub App with collaborator-management permission. That connection is separate from GitHub sign-in because GitHub Apps cannot progressively request the additional permission only when a merchant needs it. Keeping the apps separate avoids asking every Ruba user for sensitive repository access.

​
Configure the benefit

1

Start a GitHub benefit

Open Benefits, choose New Benefit, then select GitHub Repository Access.
2

Authorize the repository app

Select Connect your GitHub Account and install the dedicated app for the organization repositories that Ruba may manage. GitHub returns you to the unfinished benefit afterward.
3

Choose one repository

Select the organization repository whose collaborator list should follow this entitlement.
4

Set the collaborator role

Choose the permission Ruba should grant. Read is the default and the appropriate choice for nearly every paid-access use case.
5

Attach it to a product

Add the saved benefit to the relevant product. New qualifying purchases will then drive collaborator access automatically.

​
Repository and role constraints

Personal repositories are excluded by default because GitHub does not offer sufficiently granular collaborator permissions for them; collaborators receive write access. Contact support only if that risk is intentional for your use case. Available organization roles are Read, Triage, Write, Maintain, and Admin. Higher roles can modify progressively more of the repository, so grant them only when the product requires it. GitHub documents the exact repository-role permissions. Read-only collaborators can still open pull requests.
GitHub may count outside collaborators as paid seats on your organization plan. Check your GitHub billing model and include that cost in the product price before granting access at scale.