Provider

This guide covers Git operations for team members who create and share collections.

​

Free Features

​

Initializing Git

Initializing Git in Bruno is the first step towards managing your API collections with version control. It’s easy and quick to set up. Follow the steps below to initialize Git.

1. Launch the Bruno app.
2. Navigate to the collection you want to initialize with Git.
3. Click on the Git Icon in the top-right corner of the navbar.
4. Click the Initialize button to set up your collection with Git.

This allows you to perform other Git operations such as viewing diffs, pulling changes, and more.

​

Viewing Diffs

Before committing changes, you can view the differences between your local changes and the previous version.

1. Go to Git UI.
2. Click on any modified file to see the diff view.
3. Review the changes highlighted in the diff viewer.

​

Text-Based Diff View

The Text-Based Diff view is available in the free version. It displays changes in a traditional side-by-side or unified format, showing additions and deletions line-by-line. This is ideal for reviewing detailed code changes.

---

​

Pro & Ultimate Features

​

Visual-Based Diff View

The Visual-Based Diff view provides a more intuitive, visual representation of changes. This mode highlights modifications in a user-friendly format, making it easier to understand structural changes at a glance. You can switch between text-based and visual-based views to choose the format that best suits your workflow.

​

Connecting to Remote Repository

Once you have initialized your collection, the next step is to connect it to a remote Git repository. Bruno gives you two ways to do this:

• Create a new GitHub repository directly from Bruno — recommended for new collections. Bruno creates the repo on GitHub for you, wires up the remote, and pushes the initial commit, all without leaving the app.
• Connect to an existing repository — use this if you already have a repo on GitHub, GitLab, Bitbucket, or any other Git provider.

​

Create a new GitHub repository from Bruno

After you initialize Git in a collection that has no remote yet, Bruno shows a Create a repository on GitHub prompt in the Git UI. This lets you create the repo on GitHub, set it as the remote, and push your local branch — all in one flow.

1. Open the Git initialized Bruno collection.
2. In the Git UI, click the Create a Repo on GitHub button.
3. If this is your first time, Bruno will prompt you to sign in to GitHub (via OAuth or a Personal Access Token). Authorize Bruno to manage repositories on your behalf.
4. Fill in the Create GitHub Repository dialog:
   • Owner — choose your personal account or any organization you have access to.
   • Repository name — the name of the new repo on GitHub.
   • Description (optional) — a short summary that appears on the GitHub repo page.
   • Visibility — pick Private (you and invited collaborators only) or Public (anyone on the internet can view).
5. Click Create Repository.

Bruno will then:

• Create the new repository on GitHub via the GitHub API.
• Set it as the origin remote on your local collection automatically.
• Push your local branch to GitHub so the repo is ready for collaboration immediately.

​

Connect to an existing repository

If you already have a repository on GitHub, GitLab, Bitbucket, or any other Git provider, click the Add Remote link on the same prompt (or use the Remotes option under Quick Links) to wire it up manually. To connect Bruno to GitHub via this manual flow, you need to set up either an SSH key or a Personal Access Token (PAT) on GitHub. Follow this official GitHub guide to set it up.

1. Create an empty Git repository on GitHub (or your provider of choice).
2. Open the Git initialized Bruno collection.
3. Click on Quick Links (bottom-left corner).
4. Select Remotes from the dropdown.

5. Click the Add Remote button.
6. Enter Remote Name and URL (HTTPS or SSH) and click Save.

After completing the above steps, your collection will be connected to your remote repository. You’ll need to add and commit (see below) some changes and push them to populate the remote. Once your collection is connected to the remote repository, you can manage it directly from the Bruno app.

​

Adding and Committing Changes

Once you’ve made changes to your collection in Bruno, you can easily commit those changes using the Git UI. This allows you to track changes and collaborate with your team efficiently. Follow these steps to add and commit changes:

1. Go to Git UI.
2. Click the Add Icon to stage your changes.

3. Click the Commit Changes button.
4. Write a commit message and click Commit.

You can commit all changes in a single click by pressing the Add All Changes button.

By following these steps, your changes are now committed and tracked in Git, ready to be pushed or shared with others.

​

Pushing Changes

The GUI-based Git integration in Bruno allows both engineering and non-engineering teams to work together in a fast, efficient, and accurate manner. This integration ensures that your collections remain consistently up-to-date across all team members. Push your local commits to the remote repository with just a few clicks.

1. Go to Git UI.
2. Click the Push button.
3. Bruno opens the Push to other branches dialog and fetches your remotes and branches.
4. Select the branch you want to push to. Your current branch is selected by default and is tagged Current.
5. If your collection has more than one remote, pick the one you want from the Remote dropdown above the branch list.
6. The note at the bottom of the dialog confirms the source and destination, such as Changes will be pushed from main (current branch) to origin/main.
7. Click Push to selected branch.

Now you can see all your local changes pushed to the remote repository. If the branch you’re pushing doesn’t exist on the remote yet, Bruno creates it and sets it as the upstream branch for you with no extra steps needed.

​

When a Push Fails

If the push cannot complete, the dialog stays open and shows the Git output for the operation, and the primary button changes to Close. Close the dialog and click Push again to retry. Retrying helps with transient failures such as a network timeout or a slow remote. For failures that need a fix first rejected pushes because the remote has commits you don’t have locally, or missing credentials resolve the underlying issue and then push again. In the case of a rejected push, pull the remote changes first, then push.

​

Create a Pull Request on GitHub

From Bruno 4.2.0, you can create the pull request inside Bruno: fill in the title and description, review the commits on the branch, and submit. Bruno creates the PR against the GitHub remote and shows the resulting URL. You can also browse open and closed pull requests for the current repository without leaving the app.

​

Pull Requests in the Git UI

Git UI sidebar includes a Pull Requests item under Links, below Commits. Open it to browse open and closed pull requests for the current repository.

​

Create a pull request

Work on a feature branch, not the default branch (main or master):

1. Create a new branch and check it out.
2. Make your collection changes, then commit them.
3. Push the branch to the GitHub remote.

After a successful push, Bruno prompts you to open a pull request for that branch — for example, Create Pull Request button appears.

4. Click Create Pull Request. Bruno opens a Create PR tab.
5. Check the base and compare branches at the top of the tab. Bruno shows how far ahead your branch is and what it changes, for example 2 commits ahead, +7 -1, 1 file changed.
6. Enter a Title and a Description. The description is a rich text editor, so you can add lists, links, code, and tables.

7. Scroll down to review the Commits on the branch and the Files changed diff before you submit.

8. Click Create PR to submit, or Cancel to discard the draft.

Bruno creates the pull request against the GitHub remote and the base branch you selected, then surfaces the PR URL in the Git UI.

9. Click Open in GitHub if you want to view the pull request in the browser.

You can dismiss the prompt if you are not ready to open a PR. You can start the same flow later from Pull Requests in the Git UI sidebar. If this is the first time Bruno talks to GitHub on your behalf, sign in with OAuth or a Personal Access Token, the same way you do when creating a GitHub repository from Bruno.

​

Browse open and closed pull requests

1. Open the Git UI.
2. Under Links, click Pull Requests.
3. Switch between open and closed pull requests for the current repository.

​

Branch Creation and Checkout

With branches in Bruno, you can manage your code effectively by isolating different features or tasks.

​

Creating Branches

Follow the steps below to create branches in Bruno.

1. Go to Git UI.
2. In the bottom left corner, click on main (or the default branch name).
3. Enter a Branch Name.
4. Click the Create branch button.

Once the branch is created, you can start making changes to the branch.

​

Branch Checkout

1. Click on main.
2. Select the branch you want to switch to.

3. Now you’re switched to your selected branch.

​

Stash Changes

Stashing allows you to temporarily save your uncommitted local changes (both staged and unstaged modified tracked files) and revert your working directory to a clean state matching the last commit. This is especially useful for quickly switching context or handling urgent tasks without having to commit unfinished work.

1. Go to Git UI.
2. When you have unstaged changes, click on Stashes.
3. Enter a Stash Message and click the Stash files button.

4. Your local changes are saved temporarily so you can work on something else or switch branches without losing your changes.
5. Stashes can be viewed, deleted, or applied to restore your changes later.

​

Merge Conflict Resolution

When conflicts arise during pull or stash operations, Bruno provides a visual conflict resolution interface.

​

Conflict Detection

When conflicts are detected, Bruno provides information and options to resolve conflicts:

• Commits behind and ahead of remote
• Conflicting changes identified
• Abort - Abort the operation and restore previous state

​

Visual Conflict Editor

The conflict editor provides:

• File List - Shows all conflicted and non-conflicted files with status indicators
• Diff View - For each conflict, choose to:
  • Accept Incoming (remote version)
  • Accept Current (local version)
  • Accept Both (merge both versions)

Once all conflicts are resolved, enter a commit message and click the Lock icon to complete the merge.

---

​

Request Git History

The History tab inside the Git UI lets you browse the full commit history of any individual request. You can see every commit that touched that request — complete with commit message, author, date, and short hash — and click any commit to inspect the exact diff.

​

Viewing commit history for a request

1. Open the collection in Bruno and navigate to any request.
2. Click the History tab in the request panel (alongside Params, Body, Headers, etc.).

If Git has not been initialized for the collection yet, the tab shows the Not a git repository prompt with an Initialize Git button. Once Git is initialized and you have at least one commit, the History tab lists every commit that modified the current request:

​

Inspecting a commit diff

Click any row in the commit list to open the diff for that commit. Bruno displays the file-level diff — additions and deletions — for the selected commit. Text-based diff is available to everyone; Visual-Based Diff requires Pro or Ultimate.