Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

should not update shared misc.xml #34

Open
TrentonAdams opened this issue Apr 21, 2020 · 2 comments
Open

should not update shared misc.xml #34

TrentonAdams opened this issue Apr 21, 2020 · 2 comments

Comments

@TrentonAdams
Copy link

misc.xml is intended to have non-developer specific settings in it, i.e. settings that should be shared. As such, it's inappropriate for settings from the Limited WIP plugin to be putting settings in that file. It'd be best if an appropriate non-shared file was used. It was my understanding that the entire .idea directory should be shared, and that only workspaces.xml was not supposed to be, so perhaps put it in there? That's a user specific setup

https://intellij-support.jetbrains.com/hc/en-us/community/posts/360005054360-Get-misc-xml-from-VCS-but-do-not-track-it-by-default

Anyhow, it's cause my LimitedWIP settings to flap back and forth depending on what happens with my git repo.

@TrentonAdams TrentonAdams changed the title updating shared misc.xml should not update shared misc.xml Apr 21, 2020
@dkandalov
Copy link
Owner

I finally looked into this and it makes sense that keeping settings in misc.xml is not the best option when .idea is shared. However, I'm not sure if workspace.xml is a good alternative in case anyone wants to share the config 🤔 So maybe a separate .idea/limited-wip.xml file (at least it can be added to .gitignore)?

The whole concept of sharable vs non-sharable config is a bit fuzzy. For example, there is .idea/gradle.xml which contains config for test runner (platform or gradle) which is supposed to be shared but in practice I've seen several teams where this setting is different for each developer and using the convention above should be in workspace.xml.

@TrentonAdams
Copy link
Author

Yeah, I think it's own config probably makes the most sense. It has the added benefit that teams can choose if they want to share it or not. Maybe they are all using WIP, and want to use the same techniques to software development.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants