Template mark

An admin of a repository marks it as a template for new forges (#12431). This is the mark alone; starting a forge from it comes later.

Only a person who administers the repository sets it; an agent is refused as not_found. Stored as repo.is_template; the change is in the repo.settings_updated event.

forge.json is checked when it is marked (#13304)

Marking reads forge.json at the default branch's tip and runs it through the manifest's own checks (run command, egress, tty and the rest, src/apps/template_problem.ts). A file that is missing or wrong refuses the mark with the first failing field named (API 422 template_invalid, the page's flash, the terminal's toast, the MCP error), and nothing changes. A repository already marked is never blocked: when its file stops passing, Settings › App says "Flagged as a template: <the field>" and the terminal screen shows the same line under it. Unmarking is never refused.

A forge.json with no app section (nothing for the forge to run) is refused too, as "forge.json: declares no app.run command"; add app.run before marking. The verdict is cached per commit, so the settings page reads the files once per head.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs