Do you usally commit or ignore those files? ``` .gradle/ .idea/ bin/ build/ gradle/ gradlew g...

# getting-started

[Ryan Zidago]

Do you usally commit or ignore those files?

.gradle/
	.idea/
	bin/
	build/
	gradle/
	gradlew
	gradlew.bat

[Rob Elliot]

IDE & O/S specific files like .idea/ should be in a global ignore file in your home directory. I use ~/.gitignore_global - add this to `~/.gitconfig`:

[core]
	excludesfile = ~/.gitignore_global

[Rob Elliot]

gradle/, gradlew & gradlew.bat should be checked in - the whole point is you can checkout and run ./gradlew build and it works.

[Ryan Zidago]

Thanks Rob!

[Rob Elliot]

Anything created by the build should be in .gitignore - so definitely build.

[Rob Elliot]

There are a couple of things it can be worth checking in from the .idea directory - I have the following in `~/.gitignore_global`:

!.idea/runConfigurations
!.idea/runConfigurations/*
!.idea/externalDependencies.xml

which allows me to save required plugins and special run configurations, which may be useful to other people using IntelliJ without having an endless fight over personal configuration. For instance in a project using kotest I think it's useful to prompt another dev to install the kotest plugin. And when running the app in Intellij requires specific VM or program parameters it's useful to save that as a run configuration.

[Ryan Zidago]

Thanks. For now on, I'm working alone, but it's always good to know 😉

[Albert Chang]

gitignore.io is a handy tool.

[Ryan Zidago]

Nice! I've never heard of that but will definitely look into it in the future.