# Prevent Vscode extension from creating .ansible in my project root **URL:** \ **Category:** Get Help\ **Tags:** vscode-ansible\ **Created:** [March 21, 2025, 4:21pm UTC](https://forum.ansible.com/t/prevent-vscode-extension-from-creating-ansible-in-my-project-root/41180 "2025-03-21T16:21:51Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![tbowers](https://avatars.discourse-cdn.com/v4/letter/t/7993a0/32.png) [@tbowers](https://forum.ansible.com/u/tbowers)\ **Post date:** [March 21, 2025, 4:21pm UTC](https://forum.ansible.com/t/prevent-vscode-extension-from-creating-ansible-in-my-project-root/41180/1 "2025-03-21T16:21:51Z")
I’ve been using the Ansible Vscode extension for some time now and recently I’ve noticed that it’s been creating empty `.ansible` directories in my project root directories. Is there a way that I can prevent the extension from creating these files, or maybe configure it to write them _somewhere else_? Rather than add them to .gitignore, I’d prefer that they weren’t created in the first place. VS code version: 1.98.2 Ansible extension version: 25.3.0 ---
**Author:** ![lucian](https://avatars.discourse-cdn.com/v4/letter/l/eb9ed0/32.png) [@lucian](https://forum.ansible.com/u/lucian)\ **Post date:** [March 23, 2025, 11:24am UTC](https://forum.ansible.com/t/prevent-vscode-extension-from-creating-ansible-in-my-project-root/41180/2 "2025-03-23T11:24:42Z")
Hello @tbowers, If you follow proper dev rules with vscode, all local/cache files like `.ansible` should go in `.gitignore`. Only code and config should be versioned. Builds shouldn’t rely on local folders, that’s the job of your devops pipeline (like gitlab ci). Almost every language or tool creates temp or config files in the project folder `.venv`, `node_modules`, `.pytest_cache`, etc. you don’t commit those either. Keeping it clean avoids clutter and makes your repo predictable for everyone.