When it comes to CodeKit, there are normally global CodeKit settings that I use; however, a number of the projects that I work on often result in some minor deviation from my core settings.

For those who have used CodeKit regularly, you know that you can set per-project settings, but if you’re using a project that’s under source control, there’s likely one irritating factor that you’ve noticed.

CodeKit Settings: It’s All Under Control

The problem with placing your CodeKit project and the associated CodeKit settings under source control is that you often see something like this:

CodeKit Settings in Source Control

CodeKit Settings in Source Control

Specifically, you see the CodeKit configuration file showing up every several minutes.

Because CodeKit automatically refreshes projects every so often depending on how you have it configured, the configuration file is also updated.

Thus, it shows up as an updated file needing to be committed to work your working directory.

The other day, a friend and I were talking about this exactly issue and he was mentioning that although he loves CodeKit, he hates having the settings file constantly changing.

So, sure, you could always add `codekit-config.json` to a `.gitignore` file of your version control’s equivalent, but if you don’t update your settings that often, you can also disable the automatic updating within CodeKit itself:

Disable CodeKit Settings

Disable Auto Update of CodeKit Settings

If you notice on the Project Settings screen, there’s a checkbox for “Auto-update configuration file.”

Un-check that option to disable the auto-refresh of the CodeKit settings file and you’re gold. Easy enough (and you don’t have to deal with source control ignore files either :)).