Sharing Configurations Selectively with Repository

I am trying to share formatting settings with my team at work. We tried sharing the same settings repository and adding it via Configure > Settings Repository ...

However, there was some aggresive synchronization going on behind the scenes. We tried adding a .gitignore with everything except the formatting settings for Scala, but this just ended up resetting the settings for everyone except the formatting settings.

Is there a way to automatically synchronize _only_ the scala formatting settings across multiple users?

3 comments
Comment actions Permalink

I've got the same question.  The help talks about selectively saving IDE settings, but I don't see any way to do that with the settings repository.  I see where we can save or settings in jar files, but are we supposed to commit that somewhere?  That doesn't seem to be the way the settings repository works.  What is the list of settings the settings repository will save?

0
Comment actions Permalink

I'm using the Vim mode plugin and with automatic settings repository syncing configured, it's constantly syncing vim_settings.xml which contain things like cursor position or buffer contents.  Not only do these values change frequently, resulting in a lot of churn in the settings repository, but they could also potentially contain sensitive information (like the buffer contents) that shouldn't be committed at all.

Any ideas on how to blacklist a specific file from being synced would be much appreciated.

1
Comment actions Permalink

Thomas, it is possible, although not supported officially.

 

First, if you use multiple IntelliJ products, make sure that the settings are all synced up. Just to make sure there won't be any further changes, close all IDEs.

Now, go to any IDE's settings repository directory (e.g. "~/.IntelliJIdea2017.2/config/settingsRepository/repository"), and untrack "vim_settings.xml" (see https://stackoverflow.com/a/1274447/564509 for details). Also add "vim_settings.xml" to .gitignore (create it if it doesn't exist).

Push the changes.

 

That should do it.

 

1

Please sign in to leave a comment.