Team sync over git

Because a workspace is just a folder of text files (Workspace & storage format), you can share it with your team using ordinary git — no proprietary sync server, no Impostor account holding your requests. The Source Control panel in the sidebar brings the everyday git actions inside the app so non-terminal folks can take part too.

Team sync is a Team-plan feature (and fully available during the evaluation). On other plans the panel is visible but its actions are locked, so you can still see what it does.

Requirements

Team sync shells out to the system git — Impostor doesn’t bundle its own. If git isn’t installed the panel shows an install link:

• macOS — git ships with the Xcode Command Line Tools (xcode-select --install).
• Windows — install Git for Windows.
• Linux — install git from your distribution’s package manager.

Impostor uses your existing git credentials (SSH keys, credential.helper) — there’s nothing extra to configure and no credentials are stored by Impostor.

Turn a workspace into a shared repo

Open the workspace you want to share and, in the Source Control panel, choose Turn into a shared team repo. Impostor runs git init and writes a .gitignore that excludes the local-only .impostor/ directory (run history and per-machine state).

Then:

1. Type a message and Commit your first snapshot.
2. Paste a remote URL (create an empty repository on GitHub/GitLab/Gitea first) into Add a remote and confirm.
3. Push — from the Source Control section’s ⋮ menu. The first push sets origin/<branch> as the upstream automatically.

The everyday sync and branch actions — Pull, Push, Fetch, Refresh, and Create / Checkout branch — all live in the section header’s ⋮ menu. Pull and Push appear once a remote exists and show the behind/ahead counts (e.g. Pull (2)), staying disabled when there’s nothing to sync.

Join a teammate’s workspace

With no workspace open, the sidebar’s Clone repository… action clones a shared workspace for you: paste the repository URL, pick where to put it, and Impostor clones it and opens it as a workspace in one step. (Prefer your own tooling? Clone the repository however you like, then File → Open workspace and point Impostor at the cloned folder.)

From then on Pull and Push (in the Source Control section’s ⋮ menu) keep you in sync — commit your changes, pull theirs.

Secrets stay on your machine

Secret values never travel in git. The YAML holds only an opaque reference; the value lives in your local encrypted vault. So when you clone a teammate’s workspace, the requests arrive complete except for the secrets — which is exactly what you want.

Impostor makes filling them in easy. After opening or pulling, the Source Control panel shows a banner listing every secret that needs a value on this machine — for example Login · Bearer token — each with an inline field to set it. You can also use the variable audit to review which secret-backed values a workspace expects.

What this means in practice:

• Non-secret environment defaults (base URLs, non-sensitive flags) commit as normal and are shared with everyone.
• Secret values are per-person: the names travel, the values don’t. Each teammate supplies their own once.

Review changes with a semantic diff

Click any changed request in the panel to expand its diff. Instead of a raw YAML diff, Impostor shows what actually changed in request terms:

Method   POST → PUT
Header: Authorization   (added) Bearer …
Auth     None → Bearer

Environments and folder settings fall back to a normal text diff.

Resolve conflicts

Editing different requests never conflicts — one file per request keeps diffs clean. A conflict only happens when two people change the same request, environment, or folder settings. After a pull that leaves conflicts, the panel flags the affected items. Expand a conflicted item to:

• Keep mine — take your version.
• Keep theirs — take the incoming version.
• Copy path — copy the file path to resolve it in your own git tool.

Impostor deliberately doesn’t try to be a merge editor for anything more involved — that’s what your git client is for.

A note on trust

Pulling a teammate’s change re-arms Impostor’s script trust: any pre/post request or ƒx script whose content changed must be reviewed and re-enabled before it can run again, so a pulled change can never execute silently.