How to never add WebStorm .idea folder to git ever again

Frequently when you work with an open-source repository you might accidentally commit your .idea folder to it. Maintainers of these repositories frown upon you changing their holy .gitignore file to prevent this problem. They don't want to hear about your crazy ideas of using a closed-source, commercial, and paid-for IDE.

There is a simple trick to help that I wish I discovered years ago.

The steps are very simple:

1) Create a global .gitignore file:

touch ~/.gitignore_global

2) adding the '.idea' line to it in any way you want, but preferably with your expensive IDE:

webstorm ~/.gitignore_global # or vim ~/.gitignore_global or .. you get the point

3) and then configure git to use it:

git config --global core.excludesfile ~/.gitignore_global

That's it! You will never have to feel like a sapper on a minefield again.

Let me know if you have any questions or thoughts in the comments below.

Let us help you on your journey to Quality Faster

We at Xolvio specialize in helping our clients get more for less. We can get you to the holy grail of continuous deployment where every commit can go to production — and yes, even for large enterprises.

Feel free to schedule a call or send us a message below to see how we can help.

User icon
Envelope icon


Book a call
Loading Calendly widget...
  • Add types to your AWS lambda handler

    Lambdas handlers can be invoked with many different, but always complex, event arguments. Add to that the context, callback, matching return type and you basically start listing all the different ways that your function can fail in production.

  • How to expose a local service to the internet

    From time to time you might need to expose your locally running service to the external world - for example you might want to test a webhook that calls your service. To speed up the test/development feedback loop it would be great to be able to point that webhook to your local machine.

  • For loops in JavaScript (vs _.times)

    From time to time I still see a for loop in JavaScript codebases. Linters are frequently angry about them. Let's see how we can replace them.