2025-10-28 8:22 AM
Hello,
Long time lurker here.
First of all, thank you for the extensions, really appreciated the possibility to work directly in vscode.
I have a couple of situation, however, that are really annoying and that I would like to solve.
While developing in vscode with the extension enabled. It is sufficient to update the CMake presets in order to have the tools installed by the ST extension to make the git repository dirty.
If before committing the files to the repo a pre-commit that formats the files in a proper way then it is amplificated.
The files:
In my opinion there are two different types of settings:
There should exist a good way for switching branches and change configuration without having to worry about the extension that changes files at his willing.
Is it unclear if I can put under gitignore the content of .settings folder. Anyway I cannot place under gitignore the other two files mentioned above because I am using them for other configurations.
Thank you in advance
Solved! Go to Solution.
2026-03-29 11:52 PM
Sorry... I'm a linux user and still I have to fight with the generated files because the formatting is not the same as every automatic formatter that could be enabled will do. At least from those I tried.
Also... having absolute path names in the files means that they are basically not portable around systems.
2026-03-31 10:55 AM
Not sure if it helps in your case, but there is a setting you can put into VS Code workspace settings.json to prevent the ST extension from meddling with .clandg and compile_commands.json:
"stm32cube-ide-build-cmake.intellisense.enableAutomaticConfiguration": false