Your account
GitHub connection
Forke is Git-native to the core. Connecting GitHub is what sets your starting level and powers the whole submission flow.
Why GitHub
Your account is connected once via OAuth. A one-time analysis of your public activity helps seed your starting level (LVL 1–3), and from then on every submission flows through GitHub. Forke integrates via a GitHub App — not broad OAuth tokens — that owners install on specific repos. It requests only the minimum permissions: contents (read/write), pull_requests, checks, and metadata.
Mirror & branch model
You never push to an owner's repository directly. Instead of forking the repo per developer (which doesn't scale), Forke uses branch-based workspaces inside a single mirror. Forke sits in the middle:
Forke as the orchestration layer
Owner repo
Forke mirror · forke-workspaces
dev-{username}/task-{id}
Pull request · review pipeline
Merge · upstream PR · payout
Built-in safeguards
- Secret scanning blocks commits that add
.envfiles or hardcoded tokens. - File-scope validation auto-rejects any diff that touches files outside the task scope.
- Only the Forke system merges — no developer can merge their own work, ever.
