Introducing Environment Forking and Pull Requests in Postman
Tags: api, productivity, testing, programming
Published: 2022-04-22 07:15:32

---
title: Introducing Environment Forking and Pull Requests in Postman
published: true
date: 2022-04-01 17:50:17 UTC
tags: API, productivity, testing, programming
canonical_url: https://blog.postman.com/introducing-environment-forking-and-pull-requests/
cover_image: https://dev-to-uploads.s3.amazonaws.com/uploads/articles/y5x4p4df9i3gj245nj21.jpeg
---

At Postman, we aim to provide an intuitive way for API producers to build and iterate on APIs. We also pride ourselves on delivering a world-class experience for API consumers by simplifying the process of sending requests. [Collections](https://learning.postman.com/docs/getting-started/creating-the-first-collection/ "https://learning.postman.com/docs/getting-started/creating-the-first-collection/") and [environments](https://learning.postman.com/docs/sending-requests/managing-environments/ "https://learning.postman.com/docs/sending-requests/managing-environments/") form the basis of interaction between API producers and consumers in the [Postman API Platform](https://blog.postman.com/new-postman-api-platform-redefining-api-management-for-api-first-world/). Producers update reference collections using pull requests, and consumers can use them via forks to send requests. We have seen so many users rely on these features to develop and consume APIs.

Today, we are excited to announce the launch of [forks and pull requests for environments](https://learning.postman.com/docs/collaborating-in-postman/version-control/). You can now seamlessly collaborate on environments with the _same ease you’ve come to expect from collections_.

## Create reference environments using forks

In many cases, you need to use an environment to send a request. You might duplicate the environment or create a new one and copy over the variables. You can now simply fork an environment, with a descriptive label to indicate what is used for, and use it to send requests. Explore our [featured public workspaces](https://www.postman.com/explore/workspaces "https://www.postman.com/explore/workspaces") to find interesting collections and environments which you can fork and use.

![Forking an environment is as simple as opening the environment in a tab](https://blog.postman.com/wp-content/uploads/2022/03/Forking-an-Environment.gif)
_Forking an environment is as simple as opening the environment in a tab_

## Keep environments up-to-date with pulls

Environments, just like your APIs, are constantly evolving. You may add new variables or change their values when you add new capabilities to your API. To incorporate these changes in your copy of the environment was previously a manual process—you found out new changes and then had to copy them over.

No more! Now, after you fork an environment, if the original environment changes, you will see an option to pull new changes right from the environment tab.

![Keep your environment updated with your original environment by pulling changes](https://blog.postman.com/wp-content/uploads/2022/03/environment-pull-changes.gif)
_Keep your environment updated with your original environment by pulling changes_

## Prevent accidental changes with fork and merge

You can also use environment forks to work in a separate context and avoid making accidental changes that may have negative effects on the [mocks](https://learning.postman.com/docs/designing-and-developing-your-api/mocking-data/setting-up-mock/ "https://learning.postman.com/docs/designing-and-developing-your-api/mocking-data/setting-up-mock/") and [monitors](https://learning.postman.com/docs/monitoring-your-api/intro-monitors/ "https://learning.postman.com/docs/monitoring-your-api/intro-monitors/") using that environment. Once you are happy with the changes, simply merge them back to the original environment.

![View the diff between two environments and merge your changes](https://blog.postman.com/wp-content/uploads/2022/03/Merging-an-Environment.gif)
_View the diff between two environments and merge your changes_

## Collaborate using pull requests

Merging changes directly will work only if you have an Editor role for the original environment. If you don’t, you can always raise a pull request and ask for a review before your changes can be merged by the environment editor.

![Comment, review and collaborate with your team on Environments using Pull Requests](https://blog.postman.com/wp-content/uploads/2022/03/Environment-PR.gif)
_Comment, review, and collaborate with your team on environments using pull requests_

Head over to our [Learning Center](https://learning.postman.com/ "https://learning.postman.com") to learn more about [version control in Postman](https://learning.postman.com/docs/collaborating-in-postman/version-control-for-collections/ "https://learning.postman.com/docs/collaborating-in-postman/version-control-for-collections/"). If you have features to request or bugs to report, create a ticket on our [public issue tracker](https://github.com/postmanlabs/postman-app-support/issues "https://github.com/postmanlabs/postman-app-support/issues").

[**Try Postman now**](https://www.postman.com/downloads/ "https://www.postman.com/downloads/")

The post [Introducing Environment Forking and Pull Requests](https://blog.postman.com/introducing-environment-forking-and-pull-requests/) appeared first on [Postman Blog](https://blog.postman.com) by Ankit Jaggi.