Skip to main content
Bruno’s superpower is the ability to collaborate natively using version control systems like Git, CVS, etc, and platforms like GitHub, Gitlab, Bitbucket, etc. This gives you and your teammates confidence that a collection is current, and provides benefits of co-location if you choose to store collections directly alongside your source code. The process of collaborating on a Bruno collection is more or less the same in all of the above-mentioned platforms. For beginners, you can take a look at this tutorial on version control here. There are two ways to collaborate via native Git in Bruno:
  1. Using the terminal or command line to execute Git commands
  2. Using Bruno’s GUI-based Git functionality
Bruno 3.0.0+: Core Git UI features (init, view diffs, check for updates, pull, clone) are now available in the free version. Advanced features like commit, push, branching, and merge conflict resolution require Pro or Ultimate editions.
These approaches are documented separately for ease of access. So let’s dive into the next section.

Git Strategies

Choose how collections and code live together — co-located with your source or in a dedicated repository.

Git Providers

Provider-specific setup guides, starting with GitHub.

Fetch in Bruno Button

Embed a button in your README so anyone can open your workspace or collection in Bruno.

Collaboration via GUI

Bruno’s built-in Git interface — init, diff, pull, commit, and more without leaving the app.

Collaboration via CLI

Version and share collections with plain Git commands from the terminal.

GitLab

Collaborate on collections in GitLab repositories.

Bitbucket

Collaborate on collections in Bitbucket repositories.

Azure DevOps

Collaborate on collections in Azure DevOps repositories.