This feature has been deprecated and it’s no longer possible to create a new connection between a GitHub repo and a collection. Existing connections between repos and collections will continue to sync.
You can work on your API project files locally in Postman with Postman’s file system (Native Git) support. Learn more about Postman’s Native Git support here
Once you connect your GitHub repository and primary branch to your collection, you can fork your collection and collaborate with your team on it.
Fork a collection connected to your GitHub repository and branch
Before you get started, create your feature branch.
To fork a collection connected to your GitHub repository and branch, do the following:
- Open your primary collection.
- Next to your collection, click
View more actions. Then, click Fork. - Select a workspace.
- Confirm your fork is linked to your branch. Then, select a branch.
- Click Fork Collection.
Postman creates a collection file in the connected repository and branch. The collection’s file name is the collection ID. Each time you save your collection in Postman, your changes are committed to the connected GitHub repository and branch.
Collaborate on your collection
With GitHub and Postman, you start collaborating by forking your primary collection and making changes in Postman. Your teammates can join you and contribute to your changes. When you’re ready for your team to review your changes, you create a pull request and merge it in GitHub.
To collaborate on your collection’s next release, do the following:
- Open your forked collection and make changes to it in Postman.
- When you’re ready for your team to review your changes, create a pull request in GitHub and ask your team to review it.
- When you’re ready to merge your changes with your primary collection, merge your pull request in GitHub.
- (Optional) Delete your forked collection.
When you merge your pull request in GitHub, Postman updates your primary collection in Postman with the updates from your forked collection.