Version control in Insomnia

Uses: Insomnia

Insomnia allows you to manage versions of collections, mock servers, design documents, and global environments in Insomnia, both with cloud sync and git sync. Branches are object-specific, meaning that the branches you have in a collection are specific to that one collection. They aren’t shared with other collections or other objects, like a mock server.

With cloud sync, versions are managed only in the Insomnia UI and can be shared with other users you’ve invited to your workspace. In git sync, you can pull branches from your repository into Insomnia and can also push local branches you make in Insomnia to your repository.

Version control capabilities

Before you can manage branches, commits, and merges, click the workspace (document, collection, mock server, or global environment) from your project.

You can perform the following version control actions from Insomnia:

  • Create a branch
  • Checkout a branch
  • Commit or push changes
  • Revert changes
  • Pull changes
  • Merge a branch
  • Resolve merge conflicts

Version control is managed from the bottom left of the sidebar.

Version control sidebar menu location

FAQs

Both allow you to use version control and collaborate with your team. You should use Git sync if you’re already using a Git repository and your team requires detailed version tracking and rollback capabilities.

Yes, if you have branch protections for a branch, say main, you won’t be able to push to that branch in Insomnia.

Yes, you’ll have to pull it into Insomnia. You can push branches you make in Insomnia to your repository.

If you invite them to your organization or workspace, other users can edit the same Insomnia entities and use the same branches for version control.

Something wrong?

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!