Turns out any .gz file breaks codex.
For me I was still tracking the .yarn/ directory which contained a .gz file.
I’d suggest looking for any non-code files and make sure you arent committing anything that can mess GPT up.
Added .yarn/ to git ignore, pushed everything to a brand new repo. Reset my codex environments. Perfect after this.
I ran into the same binary files problem. In my case Codex had actually added one binary file (png file, probably it made a copy of my existing file for some reason). Noticed that when reviewed the list of files and diffs.
I asked Codex to remove that file as it should not have been added in the first place. After this it was able to create the pull request.
I sometimes have similar issues, but I do not see you describe it as exactly the same.
The issues I used to get often:
It will say ‘‘update branch’’ in the top right instead of ''create pull request".
Or it will just say create pull request, but when you do it seems to use a old PR.
To avoid these kinds of conflicts I have changed my way of working:
For each issue/update/feature I write using codex I start a new task. After having made 1 PR I make a new one. And I archive the old ones. That way you can also find old PR’s back easy if need be inside codex. Although I do not really see a practical use for that.
So in summary:
I got the same issue with a new repo. It’s my first time using Codex. Do we have a solution for this?
Hi @thuongpham,
Any chance you can show me what it says exactly? what the issue is?
See if I am right about understanding the issue.
For the “Binary files are not supported”, another option that worked for me is to:
I also point this out in my video on YouTube " Use Codex by OpenAI to Build a .NET + PostgreSQL App in 5 Steps + fix Binary files are not supported" (at 4:23)
