I was using the git integration when in Beta format without any real complications and all seemed to work well. Now I just can’t get anything to work properly. anytime I try to link a folder all the collections either have issues or when fixed are not pulled/pushed to the cloud correctly.
I tried an experiment when I IU linked an existing collection from one workspace to a a local repo and it saved things mostly well, then I created a new workspace, disconnected my repo from my previous one and linked it to the new workspace. when I tried to push the collections to the new workspace, hardly anything would link correctly and any changes made in postman would not always get pulled correctly.
This is very frustrating as it feels like in Beta it was a lot more stable
I guess the most significant change with the local mode in V12, is that only v3 of the Collection format (yaml) is supported and not the json files.
Are you able to share more visual examples of the flow and the errors that you’re currently seeing, please. It would make it easier to help see the issues you have in front of you
I have a workspace which I connected to my locally cloned repository, this meant that the postman folder was created and when I pulled from cloud the yaml files were created accordingly in the collection and environment folder
I then checked the local items view but none of these collections are visible, the env file is
I made a changes in the cloud view and pulled it and it did appear correctly in my ide
I made a change in my ide, when I went to push to cloud, it does not prompt me to update cloud and asked to create a new env while deleting the old one
Then I tried to link this (after disconnecting) repository to a new workspace in my postman but it seemed to not be able to find these collections even though the yaml file was created via the postman integration.
Ideally all of this could be better demonstrated via video call but not sure if that is possible
In addition to the above when I try to pull an existing collection from cloud to the local vie, even though I get a successful pull, these collections never show up in the view. This seems to indicate some form of conversion issue
yeah I tried that and no luck also just as a side note I am on v12 and I tried to create new collections on cloud and still the same issue happened. It’s only collections that are created on the local view that seem to show up across the board and can be pushed/pulled
The Collections that get created and can be seen in Local View, will be the v3 version and those are the only ones that are supported locally. The ones that you’re bring in could be V2 Collections and would show a warning to convert those.
I’m trying to replicate this issue on my side and it seems to be working but I might also not be doing the same thing as you are so please, point those changes out.
The strange thing is that I have created some news one on my end and when I saves them all on my local they were all converted to v3 yaml files so I am not sure what might be the reason. Also we have a lot of collections on our postman that need to be linked to the repo and then shared across the teams and this is a major blocker for us. Not sure if you guys do video calls to better help understand the issue at hand
Hi @danny-dainton I continued to investigate alone and I figured out the issues and it seems like there is a postman bug. I have asked the postman AI to summarise it based on the findings that were made:
Thanks a lot so it seems it was the .resource file all along, how come this was not created immediately when pulling from cloud? could it be a postman bug?
That’s a really good question, and yes — it does look like a Postman bug (or at minimum an incomplete feature in the local/git-linked workspace mode).
Here’s what likely happened:
What should have happened
When you pull a collection from the cloud into a git-linked local repository, Postman should scaffold the full correct folder structure, including the hidden .resources/definition.yaml file. That file is what tells Postman “this folder is a collection”, so without it, Postman simply doesn’t recognize the folder at all.
What actually happened
Postman pulled down the request files (the .request.yaml files) but skipped creating the .resources/ folder and definition.yaml. This left the collection folders in a broken state — present on disk but invisible to Postman’s local view.
Why it’s likely a bug
When you create a collection locally (like your New Collection), Postman correctly generates the .resources/definition.yaml — so it clearly knows the format.
But when pulling from cloud, that same scaffolding step was apparently not triggered, meaning the cloud-to-local sync path has a gap in it.
This is consistent with what you saw: push didn’t work either, because Postman never “saw” those collections as valid local entities to begin with.
What to watch out for going forward
Until this is fixed by Postman, any time you pull a new collection from the cloud into your local repo, check whether .resources/definition.yaml was created inside the collection folder. If it’s missing, you now know the fix — just create it manually with:
Thank you for taking a closer look at this on your side and providing the explanation.
As some old Collections can be V2 JSON and when pulling those from the Cloud View, there is a migration step which convert those into the new V3 Yaml format. This also comes with those additional folders and files as config.
We have been releasing certain fixes around that flow in version 12.0.4 which would handle most case but there still appears to be some Collections that are causing issues.
When you are pulling or created Collections and other elements into the Local View, you’re creating new files in the local git enabled folder, checking the Files section in the app of in your local file system is a good place to start.
I’ll give this information to the team to see what else could be happening here.
We are having the same issue and 12.0.4 does not fix it. We have a significant number of Postman licenses and use Postman collections for a lot of things and we have Pipeline checks and what-not. We can’t just go convert all of our json to yaml overnight. You have to continue backwards support for json. This has to be prioritized to the highest and solved as soon as possible.
Are you committed to solving the issues quickly?
Should we advise all our team members to downgrade for now?
Same issue here. Collections are displayed in cloud view but in local view they are not.
Env and other items work well. Only collections are not displayed. File system looks fine.
Hey, so I have updated to 12.1.1 and it seems a number of issues where fixed but when I push to cloud any changes done locally these are never pushed, no matter how often I try, in fact in the history section this is never registered.
On the other hand any changes done in cloud and pushed are picked up correctly and without issues. This is a bug in itself which I tested a number of times now and even followed all possible edge cases that could impact it
I’m from the Engineering team. Let me help you with the issues you are facing. Could you check if the Collections/Environments in the sidebar are showing up in the workspace history tab?
We fixed a couple of issues in the patch versions. To eliminate any issues carried over from the previous versions, could you try deleting the collections and pulling them from cloud again.
Also, happy to jump on a call to walk through if you are available.
Hey Kamalakannan, so I have seen them and yes they do show in the history tab, though maybe a very quick call could be more useful at this point as even the AI agent seemed to flag this as a bug
also just as a side note I am on v12 and I tried to create new collections on cloud and still the same issue happened. It’s only collections that are created on the local view that seem to show up across the board and can be pushed/pulled
