Open coreyog opened 2 years ago
@coreyog thanks for reaching out. We are working on building the flow that you described. Would it be possible to get onto a short call to discuss your exact workflow and see if the solution that we have fits your need? You can schedule a call with us using this link.
@coreyog Happy to announce that with the launch of Postman V10, you should now be able to achieve the workflows you described. You can now, work directly on your branches from Postman and pull, push, switch branches, and create branches as desired. Read my blog post to know more. Reach out to me on shashank.awasthi@postman.com or schedule a call with me using this. I can walk you through the flow and enable the experience for your team as we are rolling this out slowly.
Is there an existing request for this feature?
Is your feature request related to a problem?
The provided solutions for backing up collections, requests, and environments are extremely hard to stay synchronized with the in-development API Repo being hit. Staying current kinda works, but history becomes impossible to parse. The branches and commits would need to match up 1:1 and that's not easy.
Describe the solution you'd like
It has been easier, albeit not easy, to export all our collections when we're done working a branch and include those JSON files in our code repo. Then anytime you pull latest or jump to a new branch, you delete everything and reload the files from the repo. This however results in people forgetting to export their data before committing or forgetting to import after pulling. If Postman saved and loaded collections and environments to/from files that are under a custom folder (i.e. our repo folder) then every single commit in our repo will have up to date collections, requests, and environments going forward. I would love to be able to pull my code repo and see Postman update with requests my peers wrote, or when I push I'll know they won't be ill-equipped to test out the new endpoints I just added.
Describe alternatives you've considered
We've tried committing our Postman data and using it like a second git repo but that only works well with the bleeding edge of our code and our requests. Go back a week in one or the other and it's hard to find compatible collections for the codebase.
Additional context
No response