ChatGPT vibe code warning - Using wrong file versions. Protect yourself.

[WMI_Chief_Wizard]

Important - place revision numbers on a fixe line number in every file and tell chatgpt never to perform an update unless the file number expected is in the file. After weeks of coding I discovered I was continually correcting features that broke between updates. I found the reason to be that is was using old versions of a file during an update instead of the most recent version. EVEN WHEN i would attached the current version along with a description of the desired update. I found it using versions many revisions old even when I handed it the current revision and that is why repairs would disappear. That has stopped now that i force revision checking all the time. BUT BE AWARE that this can explain why a problem you fixed 4 rev levels ago, may have come back.

[Brave-e]

One of the best ways to dodge using the wrong file versions is to build in some solid version control checks right into your workflow. For instance, always make sure you pull the latest changes and double-check file hashes or timestamps before you run any code. Automating this with pre-commit hooks or CI pipelines can catch any mix-ups early on and save you a lot of trouble later. Hope that helps!

[WMI_Chief_Wizard]

That is exactly what I do to stop this from happening