RoleLogic

HomeIntegrations › GitHub Contributor Role

GitHub Contributor Role icon

Reward GitHub Contributors With Discord Roles

Members link Discord and GitHub once. RoleLogic checks contributions to your repo — commits, PRs, merged PRs, issues — and auto-grants Discord roles when they cross the threshold you pick.

Free plan available · No coding required Version 1.0.9 Updated 2026-04-17
githubcontributorcommitspull requestsmerged prsissuesopen sourcehackathondevelopergithub oauthrolediscord serverdiscord role bot

What you can build with GitHub Contributor Role

Real use cases that ship in production Discord servers using RoleLogic + GitHub.

Open source contributor recognition

Auto-grant a 'Contributor' role at 1+ merged PR, 'Core Contributor' at 10+, 'Maintainer' at 50+. No manual badge handouts in #verification, no out-of-date contributor lists.

Hackathon and bounty events

Set up contribution rules for a hackathon, bounty push, or sprint. Roles auto-granted as participants hit the count you defined and removed when the event ends if you swap the rule.

Issue triage and reporter rewards

Reward members who file useful bug reports — 'Bug Hunter' at 5+ issues, 'Power Reporter' at 20+. Use a range condition (between 5 and 20) to scope a tier exactly.

Per-repo gating across multiple projects

Run a separate role link per repo so roles map to specific projects — useful for organizations with multiple OSS projects, monorepo subdirectories, or layered Discord communities.

How GitHub Contributor Role works

From install to live GitHub roles in a few minutes.

1

Pick a public GitHub repo

Enter the owner/repo of the project you want to track. Public repositories only — GitHub's API doesn't expose private contribution data without elevated access.

2

Set the condition

Choose the metric (commits, PRs, merged PRs, or issues) and an operator: =, >, >=, <, <=, or 'between' for a range. One condition per role link.

3

Members link GitHub via OAuth

Members sign in with GitHub once. RoleLogic matches contributions on the verified email tied to their GitHub account, so commits attributed to that email show up automatically.

Get started — it's free

Frequently asked questions

Common questions about GitHub Contributor Role and RoleLogic.

Does it work with private repositories?

Public repos only. GitHub's REST API doesn't expose contribution counts on private repos without elevated app permissions, and most communities want a public source of truth anyway.

What contributions count?

Commits, pull requests (all), merged pull requests, and issues. You configure which metric matters and the threshold — including range conditions like 'commits between 5 and 50'.

Why is my contribution count zero even though I committed?

Commit attribution on GitHub depends on the commit email matching a verified email on your GitHub account. If you committed with a different email, GitHub won't credit it to your account and the plugin can't either. Add the commit email to your GitHub profile and re-sync.

How often is contribution data refreshed?

On a background schedule, typically every couple of hours per member. Roles update automatically when new contributions push members across thresholds.

What about GitHub API rate limits?

RoleLogic uses an authenticated GitHub token (5,000 requests/hour) and batches requests under a configurable budget — default 4,500/hour — so quota is never exhausted.

Ship GitHub Contributor Role in 5 minutes

Free plan, no coding, real-time sync. Used by Discord servers of every size — from indie communities to verified gaming servers with hundreds of thousands of members.

Set up GitHub Contributor Role