Share a workspace with Git
Fetchpier stores everything as plain text, so you can use Git for all collaboration: branches, reviews, and diffs.
git add users/ auth/git commit -m "feat: add user and auth endpoints"git pushWhat to version and what not to
Section titled “What to version and what not to”Fetchpier assumes this split by default and writes a matching .gitignore when you create a workspace:
| Path | Version it | Why |
|---|---|---|
requests/**/*.http | Yes | These are your requests — part of the code. |
.fetchpier/settings.json | Yes | The team’s shared HTTP configuration. |
environments/<env>/config.json | Depends | Version it if it holds no secrets. For ones that do, use an ignored environments/local/ folder. |
requests/.runs/ | No | Local per-send log. Fetchpier adds it to .gitignore by default. |
environments/<env>/.state/ | No | Per-environment state, including the cookie jar — often sensitive. Ignored by default. |
Code review
Section titled “Code review”.http files diff cleanly because each request is a sequence of METHOD URL lines plus headers and
body. Your team reviews API changes in the same pull request as the code that consumes them.
Branches
Section titled “Branches”Each developer can keep their own branch with in-progress requests. When you merge to main,
Fetchpier’s watcher reloads the tree automatically if the workspace is open.
Tip: # @id for stable diffs
Section titled “Tip: # @id for stable diffs”When you save a request from the UI, Fetchpier writes a # @id <uuid> at the top of the file. Keep
it: the app uses it to identify the request across renames, which makes diffs more stable instead of
producing a “deleted file + new file”.