Getting started
For developers
Forke is developer-only. Your code does the talking — no proposals, no interviews.
Sign up & connect GitHub
Sign up via the “Do Tasks?” path with Google or GitHub — the developer path is open access, no application required. Connecting GitHub once via OAuth runs a one-time automated analysis of your public activity that seeds your starting level (LVL 1–3); a 60-second skill self-assessment then personalises your feed. You have a 7-day nudge window to connect GitHub if you signed up with Google.
Your journey
Browse the feed
See bounties gated to your level, skill tier, and trust score — you only ever see what you're eligible to claim.
Claim a task
Claiming opens a 20-minute soft reservation. Activate it by creating a branch, your first commit, or pressing “I'm Working” — the task then locks to you and the deadline clock starts.
Build in a branch
Work in a Forke-managed branch (dev-{username}/task-{id}) inside the Forke mirror — never directly on the owner's repo. Stay inside the file scope; edits outside it are auto-rejected.
Submit a PR
Open a PR and fill the FORKE_SUBMISSION.md template. Automated checks and an AI review run before the owner sees anything.
Get paid
On approval, Forke merges upstream, releases escrow to your UPI instantly, and awards XP — and the task lands on your public profile.
Tips for your first task
- Pick something inside your skill tier — a clean first submission boosts trust score.
- Read the acceptance criteria before claiming; scope creep gets auto-flagged.
- Submit early — beating 50% of the deadline earns a
+25 XPspeed bonus. - Don't claim what you can't start — abandoning after activation is a strong trust-score negative.