Is anyone having trouble pulling changes to the forked Postman collections? I get a lot of conflicts when pulling and, even if I resolve them (I’ve tried keeping the source and the destination with the same results), the changes are not merged. @philip-ellis, Colin said that you might have information about a new way to pull changes so that I don’t have to re-fork every few days. Any pointers would be great, thanks!
Because of a huge number of changes, postman might not allow you to pull them all at once (The postman API will timeout on large changesets). You should be able to create a new fork and then pull changes as they come in from now on as we have made changes to the collection so that it incrementally updates with API changes now
@philip-ellis Was this change made in the last few days because I just recreated the fork yesterday or last Friday. The issue doesn’t seem to be related to the number of changes because on the Beta collection I keep getting the same 27 entities modified or conflicted that do not merge. On V3, they are the same four entitles every time. Most of these APIs are not ones that I have modified in my collection, either, so I am not sure why there is a “conflict” on them.
There was a large change added on Friday, but after that, you should see less changes coming in. I wouldn’t expect there to be conflicts if you didn’t change anything on your end, but we don’t have any control over how Postman handles changesets. We are monitoring and will be working to improve this process over time.
I’ve found that I’ve had to delete the fork and recreate it when large changes like this happen. It’s unfortunate but it seems like postman doesn’t handle huge change sets very well.
2 Likes
That’s exactly right—Postman APIs seem to not handle larger sets of APIs well.