Reviewing

Review Policy by Source

Choose how much review a change needs based on where it came from.

Three lanes

Open a folder's settings and you'll see up to three review lanes:

The Local edits lane has three modes: Needs approval, Hybrid, or Auto-accept (see Accepting and Rejecting Changes). The two remote lanes are set to land instantly or need approval. Only the lanes that actually apply to your workspace show up.

What about Google Drive?

Files synced with Google Drive don't get their own lane. When a Drive pull updates a file, Stet sees it as an ordinary external edit, so it flows through the Local edits lane and follows that setting.

Why stet sync is different

Stet sync knows who each collaborator is and what role they have (Owner, Editor, and so on), because sign-in is verified. That means you can set rules by person or by role: "Alice's changes land instantly," or "Editors need approval." GitHub can't offer that same guarantee — anyone with push access to the repo can commit as anyone — so GitHub gets one rule for the whole connection instead of per-person rules.

Workspace rules vs. your own settings

For a shared stet-sync workspace, the owner sets review rules once, in Share Settings, and everyone in the workspace sees the same rules. Your own local settings can only add caution on top of the workspace rule — you can require more review for yourself than the workspace asks for, but never less.

Current limit: if you're the workspace owner, your own local settings still control your own changes — a workspace rule that would ask for approval on owner changes doesn't yet apply to your own edits. This is being closed in a future update.

Where you see it

The folder inspector shows one lane per source with a small dot if the lanes disagree with each other. A lane that says "Uses remote default" is inheriting from a broader setting rather than being configured directly.