Forke Docs

Learn what Forke is and how to get from sign-up to your first payout.

The vocabulary that shows up everywhere on Forke — bounties, escrow, levels, trust.

The end-to-end journey from connecting GitHub to your first instant payout.

Post scoped tasks, fund escrow, and review a clean verdict instead of raw code.

Your public developer page, activity graph, completed task history, and badges.

Why Forke needs GitHub access, what permissions are requested, and how PRs are mapped.

Manage your profile details, notification preferences, and UPI ID for instant payouts.

How to filter tasks by tech stack, level, reward, and estimated completion time.

How task reservation works, the 20-minute timer, and what happens when you activate.

How Forke creates dedicated working branches and why developers never push directly to main.

How to link your PR, run pre-submission validation, and trigger the automated review pipeline.

Static analysis, AI test generation, security scanning, and owner verdict card generation.

How Forke translates code diffs into plain-English acceptance signals for task owners.

Best practices for founders writing task specs that AI reviewers and developers can test against.

How XP is earned from completed tasks, speed bonuses, clean reviews, and streak multipliers.

Full tier breakdown from Level 1 Newcomer to Level 25 Forke Legend and what each tier unlocks.

Frontend, Backend, Fullstack, and DevOps tracks that gate specialized bounty categories.

How deadline adherence, review pass rates, and dispute history calculate your Trust Score.

How owner funds are locked before a bounty goes live and how instant payouts trigger on approval.

What happens when a task expires, how refund requests work, and the 48-hour dispute window.

Rules against plagiarized code, ghosting claimed tasks, circumventing escrow, or alt accounts.

How to open a support ticket, appeal a dispute, or reach the engineering team directly.