Forke branch workflow

You get an isolated, Forke-managed branch. Just code.

Where you work

After activating, work in dev-{username}/task-{id} inside the Forke mirror (the forke-workspaces org). Your branch is created off the task base branch (task/{id}-{slug}) — when you're done, your PR targets the task branch, never main. PRs aimed at the wrong branch are rejected automatically.

Stay in scope

Each task defines an allowed file scope. Forke validates every PR diff against it and auto-rejects anything that touches files outside the allowed paths or inside excluded ones (like .env, auth, or secrets). This is the single most important security feature in the submission pipeline — and it protects you too, by keeping your changes focused.

Three principles

1. Never ZIP uploads. Every submission lives in a PR. No exceptions.
2. Forke is the middle layer. Developers never touch owner repos directly.
3. AI assists, humans decide. AI generates the verdict; owners make the call.