2025-05-12 7:50 PM
With every rollout of the new and improved, patched together, Frankenstein IDE we all love and to a certain degree, depend on. STM32CubeIDE comes with new surprises! I had been working on a project for the last couple of months with a previous version of Frankenstein. Now I only use it for the CubeMX and flashing/debugging/SWV capabilities while all coding happens in VSCode. My existing .gitignore file was working fine and was able to share work with others no problem. It didn't matter what version of Frankenstein they had, it would work. Then, I had the brilliant idea of finally updating to the latest version of the IDE the other day and quickly realized it was not such a brilliant idea. I have been jumping through hoops, watching every video I can, trying to understanding the new file structure (yes my .gitignore excludes .settings/ and .metadata/ already) yet I can't figure out why when I create a branch in VSC to test a feature, then merge it with the previous branch I was working on, it breaks the entire code. The error logs from both git and the IDE could fill a library. Does anyone have any good .gitignore templates for the STM32CubeIDE v1.18.0? Or have any resources you found helpful in getting away from the IDE entirely? It has halted progress on my project who's deadline is coming up and any tips, resources, wives tales, etc.. about how to figure out how to not have it break my projects every time there is an update would be much appreciated!