RequestTailor Preview (22 November 2026): requests as files in Git, no account, offline – on the Mac, in the browser and in the pipeline. What’s inside → +43 664 1964199Contact →

Git

Because every request is a file, Git is the natural way to share and review collections. The Git sidebar shows what changed and commits without a staging area: pick the files, write a message, done. Before every commit a scanner checks whether credentials are typed into the files in plain text.

Edition
Free
Where
Git sidebar or Show Git in the command palette
Commit
without a staging area: pick files, message, Commit
Mac app
Git built in (gitoxide)
Web app
isomorphic-git; network via rt agent

View changes

The Git sidebar shows the branch at the top and whether it matches the remote, the changed files below. Click a file to open its diff.

Git sidebar with branch main, in sync with origin/main, two changed files health.yml and users/list-users.yml, above it a diff of health.yml where the method changes from GET to HEAD
The Git sidebar with the diff of a changed file.
  1. Branch and its state against the remote, for example in sync with origin/main.
  2. Switch branch, New branch, Pull and Push.
  3. The changed files with checkboxes; M means modified.
  4. The diff shows exactly the changed line.

Because RequestTailor writes unchanged parts byte-identically, the diff contains only what you really changed – no reordered fields, no new blank lines.

Commit without a staging area

Git sidebar with two ticked files, the commit message Health check uses HEAD, the Commit 2 files button and Recent commits below
Commit: tick the files, write a message, click Commit.
  1. Save your changes with Mod+S.
  2. In the Git sidebar, tick the files that go into the commit.
  3. Write a commit message.
  4. Click Commit; the button names the number of files, for example Commit 2 files. The new commit appears under Recent commits.
  5. Send it to the remote with Push.

There is no staging area: what is ticked goes into the commit. If you want finer control over Git, use any other Git tool on the same folder; RequestTailor simply reads the files.

Secret scanner

Before every commit from the app, RequestTailor looks for credentials in the files: known token formats, private keys, Bearer and Basic credentials, passwords in URLs and values of fields that look like credentials. With findings, the app refuses the commit and names file and line. Variables, masks such as *** and placeholders are not findings.

The fix is almost always a secret variable (secret variables). If a line really is not a credential, mark it with the comment # rt-scan:allow; rt-scan:allow-next-line on its own line applies to the next one. For pipelines and Git hooks the same scanner exists as rt scan (rt scan).

Branches, pull and push

In the menu below the branch you switch branches; New branch creates one. Pull fetches and merges, Push sends your commits. Anything that changes working files – switching branches, pulling, resolving a conflict – is refused while there are unsaved changes; save first. Afterwards the app reads the folder again.

If the collection is not in a repository yet, the sidebar offers Initialize repository; Clone another repository… clones a repository into a new folder.

Resolve conflicts

If a pull leads to conflicts, the sidebar marks the affected files. For each file you choose a side: Use ours (this branch) or Use theirs (incoming). Or you fix the file by hand, save and commit again; the commit completes the merge.

In the web app

The web app uses Git in the browser (isomorphic-git). Commit, branches and diff run locally; pull and push need the network to reach the remote and therefore go through the rt agent companion (Companion rt agent).

See also

Sources on this page

The superscript numbers in the text point here. Tap one to see the source right where it is used; all sources of this website are listed on one page.

  1. 1

    Byte-identical round trip, 86 Bruno collections ↑Product · RequestTailor core repository, testdata/collections/bruno, crates/rt-format (Round-Trip-Tests) · checked on 2026-11-22

  2. 2

    Git in the app, without a staging area ↑Product · RequestTailor core repository, crates/rt-git (gitoxide), CLAUDE.md (App, Welle 4) · checked on 2026-11-22

  3. 3

    Secret scanner before every commit ↑Product · RequestTailor core repository, crates/rt-app (secret_scan), crates/rt-cli/README.md (rt scan) · checked on 2026-11-22

Frequently asked

Short answers.

Does RequestTailor have a staging area?
No. You tick the files that go into the commit, write a message and commit. For finer control use any other Git tool on the same folder.
Why does RequestTailor refuse my commit?
The secret scanner found plain-text credentials. The message names file and line; turn the value into a secret variable or mark a harmless line with # rt-scan:allow.
Why can I not switch branches?
There are unsaved changes. Switching branches, pulling and resolving conflicts change working files and therefore wait until you have saved.

Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Get in touch

Contact

Requests in the repo instead of an account? Talk to us.

Free is free and stays free. For an early copy, for Enterprise, for the OData plugin on your SAP system or for a wish for Pro and Team: write to me. I reply within one working day, personally.

Martin KochManaging Director, CloudDNAI read every request myself and reply personally.