Skip to main content
The Git panel carries the current branch’s history, and every commit and changed file in it opens as a read-only diff tab beside your requests. Reading what changed never leaves the app. Git applies to local projects only, so the Git tab is hidden while a team project is active.
Git requires the desktop app. Download Requestly.

Open the Commits section

Commits is the first of the three sections below the file area of the Git panel, above Stashes and Remotes. Click its header to expand it, and click again to collapse. The number at the right of the header is how many commits the current branch’s history holds. It renders only once the branch has at least one commit, so a branch with none shows the Commits header on its own. Requestly loads the history when you expand the section, so a collapsed section costs nothing.
The three sections are hidden while a merge is in progress, because the panel gives the whole file area to resolving the conflict.

Read the commit graph

Expanded, the section draws the history as a graph, newest commit at the top. Each row is one commit.
Rows work from the keyboard. Tab to a commit, then press Enter or Space to open its diff.
The expanded Commits section showing a count of five in its header and five commit rows, each with a graph dot, a short id, a message, and an up arrowThe expanded Commits section showing a count of five in its header and five commit rows, each with a graph dot, a short id, a message, and an up arrow
Scroll the section to load older commits, fifty at a time, up to five hundred loaded at once. The history reloads on its own after you commit or pull while the section is open. Collapsing drops the loaded commits, and expanding again starts from the newest.

When the section has nothing to show

The expanded Commits section on a branch with no commits, its header carrying no number and its body reading No commits yetThe expanded Commits section on a branch with no commits, its header carrying no number and its body reading No commits yet

Open a diff

Three places in the Git panel open a diff, and each one opens a tab beside your requests. A stash in the Stashes section opens the same kind of tab, for the files that stash captured. See Stash changes. The tab is named after what it holds: Diff · 1a2b3c4 for a commit, and Diff · <file name> for a single file. Several diffs can stay open at once, and closing the tab is how you dismiss one.
A commit diff tab stacking one collapsible section per changed file, each headed with the file path and an A chip, with every line shown as an additionA commit diff tab stacking one collapsible section per changed file, each headed with the file path and an A chip, with every line shown as an addition
A merge commit’s diff shows what the merge brought in, measured against the branch it was merged into. Plain Git prints nothing at all for a merge commit, so this is the more useful answer.

Read a diff

A diff tab stacks one section per file. Each section starts with a header carrying the file path and a one-letter chip, and holds the line-by-line comparison below it. Click the header to collapse a file you have finished with. The chip uses the same letters as the change list, described under Status letters. Hover it for the full word. One letter differs: a file Git has never tracked shows the letter A here, because a diff has nothing earlier to compare it against, though its tooltip still reads Untracked.
A single-file diff tab for a query params file, headed with its path and an M chip, showing the removed and added lines in one column beside the Git panelA single-file diff tab for a query params file, headed with its path and an M chip, showing the removed and added lines in one column beside the Git panel
A diff is read-only. Nothing you do in the tab changes a file, stages anything, or touches a commit.

When a diff has nothing to show

A commit that changed no files reads “No file changes in this commit.” A diff that cannot be read shows the reason and a Retry button. The Git overview lists the messages Requestly can show, with what each one means.

Next steps

Push and pull

Send the commits carrying an up arrow to the remote, and bring your teammates’ work in.

Switch and create branches

Open the branch picker to switch, create, or delete a branch.