Which IDEA files belong in version control?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Intellij IDEA creates a bunch of files in .idea/
. Which ones need to be in version control?
I found the following suggested .gitignore
entries:
.idea/**/workspace.xml
.idea/**/tasks.xml
.idea/**/usage.statistics.xml
.idea/**/dictionaries
.idea/**/shelf
Currently have the following in version control - are all of these necessary?
./idea/misc.xml
./idea/modules.xml
./idea/vcs.xml
And IDEA just created this file and added it to version control, where it seems to me like it does not belong?
.idea/uiDesigner.xml
intellij-idea
add a comment |
Intellij IDEA creates a bunch of files in .idea/
. Which ones need to be in version control?
I found the following suggested .gitignore
entries:
.idea/**/workspace.xml
.idea/**/tasks.xml
.idea/**/usage.statistics.xml
.idea/**/dictionaries
.idea/**/shelf
Currently have the following in version control - are all of these necessary?
./idea/misc.xml
./idea/modules.xml
./idea/vcs.xml
And IDEA just created this file and added it to version control, where it seems to me like it does not belong?
.idea/uiDesigner.xml
intellij-idea
1
Easy way to find out: open up the file and see what's in it. If it's specific to your application, commit it.
– 3Dave
Nov 21 '18 at 19:14
1
@3Dave Not really. Most of them are specific to my application, but many of them are also specific to the current user, and some seem to be possible to delete entirely without any problem.
– rwallace
Nov 21 '18 at 19:17
Did you see this document?
– CrazyCoder
Nov 21 '18 at 19:54
add a comment |
Intellij IDEA creates a bunch of files in .idea/
. Which ones need to be in version control?
I found the following suggested .gitignore
entries:
.idea/**/workspace.xml
.idea/**/tasks.xml
.idea/**/usage.statistics.xml
.idea/**/dictionaries
.idea/**/shelf
Currently have the following in version control - are all of these necessary?
./idea/misc.xml
./idea/modules.xml
./idea/vcs.xml
And IDEA just created this file and added it to version control, where it seems to me like it does not belong?
.idea/uiDesigner.xml
intellij-idea
Intellij IDEA creates a bunch of files in .idea/
. Which ones need to be in version control?
I found the following suggested .gitignore
entries:
.idea/**/workspace.xml
.idea/**/tasks.xml
.idea/**/usage.statistics.xml
.idea/**/dictionaries
.idea/**/shelf
Currently have the following in version control - are all of these necessary?
./idea/misc.xml
./idea/modules.xml
./idea/vcs.xml
And IDEA just created this file and added it to version control, where it seems to me like it does not belong?
.idea/uiDesigner.xml
intellij-idea
intellij-idea
asked Nov 21 '18 at 19:10
rwallacerwallace
9,7242175155
9,7242175155
1
Easy way to find out: open up the file and see what's in it. If it's specific to your application, commit it.
– 3Dave
Nov 21 '18 at 19:14
1
@3Dave Not really. Most of them are specific to my application, but many of them are also specific to the current user, and some seem to be possible to delete entirely without any problem.
– rwallace
Nov 21 '18 at 19:17
Did you see this document?
– CrazyCoder
Nov 21 '18 at 19:54
add a comment |
1
Easy way to find out: open up the file and see what's in it. If it's specific to your application, commit it.
– 3Dave
Nov 21 '18 at 19:14
1
@3Dave Not really. Most of them are specific to my application, but many of them are also specific to the current user, and some seem to be possible to delete entirely without any problem.
– rwallace
Nov 21 '18 at 19:17
Did you see this document?
– CrazyCoder
Nov 21 '18 at 19:54
1
1
Easy way to find out: open up the file and see what's in it. If it's specific to your application, commit it.
– 3Dave
Nov 21 '18 at 19:14
Easy way to find out: open up the file and see what's in it. If it's specific to your application, commit it.
– 3Dave
Nov 21 '18 at 19:14
1
1
@3Dave Not really. Most of them are specific to my application, but many of them are also specific to the current user, and some seem to be possible to delete entirely without any problem.
– rwallace
Nov 21 '18 at 19:17
@3Dave Not really. Most of them are specific to my application, but many of them are also specific to the current user, and some seem to be possible to delete entirely without any problem.
– rwallace
Nov 21 '18 at 19:17
Did you see this document?
– CrazyCoder
Nov 21 '18 at 19:54
Did you see this document?
– CrazyCoder
Nov 21 '18 at 19:54
add a comment |
1 Answer
1
active
oldest
votes
For a couple of years I was a supporter of using a specific .gitignore
for IntelliJ with this suggested configuration.
Not anymore.
IntelliJ is updated quite frequently, internal config file specs change more often than I would like and JetBrains flagship excels at auto-configuring itself based on maven/gradle/etc build files.
So my suggestion would be to leave all editor config files out of project and have users configure editor to their liking. Things like code styling can and should be configured at build level; say using Google Code Style or CheckStyle directly on Maven/Gradle/etc.
This ensures consistency and leaves editor files out of source code that, in my personal opinion, is where they should be.
2
I agree with this. All my IntelliJ projects use Maven or sbt and I don't check in any IntelliJ project files. All important settings are handled by Maven/sbt, and IntelliJ can pick them up from there.
– Thilo
Nov 24 '18 at 9:31
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53419030%2fwhich-idea-files-belong-in-version-control%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
For a couple of years I was a supporter of using a specific .gitignore
for IntelliJ with this suggested configuration.
Not anymore.
IntelliJ is updated quite frequently, internal config file specs change more often than I would like and JetBrains flagship excels at auto-configuring itself based on maven/gradle/etc build files.
So my suggestion would be to leave all editor config files out of project and have users configure editor to their liking. Things like code styling can and should be configured at build level; say using Google Code Style or CheckStyle directly on Maven/Gradle/etc.
This ensures consistency and leaves editor files out of source code that, in my personal opinion, is where they should be.
2
I agree with this. All my IntelliJ projects use Maven or sbt and I don't check in any IntelliJ project files. All important settings are handled by Maven/sbt, and IntelliJ can pick them up from there.
– Thilo
Nov 24 '18 at 9:31
add a comment |
For a couple of years I was a supporter of using a specific .gitignore
for IntelliJ with this suggested configuration.
Not anymore.
IntelliJ is updated quite frequently, internal config file specs change more often than I would like and JetBrains flagship excels at auto-configuring itself based on maven/gradle/etc build files.
So my suggestion would be to leave all editor config files out of project and have users configure editor to their liking. Things like code styling can and should be configured at build level; say using Google Code Style or CheckStyle directly on Maven/Gradle/etc.
This ensures consistency and leaves editor files out of source code that, in my personal opinion, is where they should be.
2
I agree with this. All my IntelliJ projects use Maven or sbt and I don't check in any IntelliJ project files. All important settings are handled by Maven/sbt, and IntelliJ can pick them up from there.
– Thilo
Nov 24 '18 at 9:31
add a comment |
For a couple of years I was a supporter of using a specific .gitignore
for IntelliJ with this suggested configuration.
Not anymore.
IntelliJ is updated quite frequently, internal config file specs change more often than I would like and JetBrains flagship excels at auto-configuring itself based on maven/gradle/etc build files.
So my suggestion would be to leave all editor config files out of project and have users configure editor to their liking. Things like code styling can and should be configured at build level; say using Google Code Style or CheckStyle directly on Maven/Gradle/etc.
This ensures consistency and leaves editor files out of source code that, in my personal opinion, is where they should be.
For a couple of years I was a supporter of using a specific .gitignore
for IntelliJ with this suggested configuration.
Not anymore.
IntelliJ is updated quite frequently, internal config file specs change more often than I would like and JetBrains flagship excels at auto-configuring itself based on maven/gradle/etc build files.
So my suggestion would be to leave all editor config files out of project and have users configure editor to their liking. Things like code styling can and should be configured at build level; say using Google Code Style or CheckStyle directly on Maven/Gradle/etc.
This ensures consistency and leaves editor files out of source code that, in my personal opinion, is where they should be.
answered Nov 24 '18 at 9:18
FrankieFrankie
19k1061104
19k1061104
2
I agree with this. All my IntelliJ projects use Maven or sbt and I don't check in any IntelliJ project files. All important settings are handled by Maven/sbt, and IntelliJ can pick them up from there.
– Thilo
Nov 24 '18 at 9:31
add a comment |
2
I agree with this. All my IntelliJ projects use Maven or sbt and I don't check in any IntelliJ project files. All important settings are handled by Maven/sbt, and IntelliJ can pick them up from there.
– Thilo
Nov 24 '18 at 9:31
2
2
I agree with this. All my IntelliJ projects use Maven or sbt and I don't check in any IntelliJ project files. All important settings are handled by Maven/sbt, and IntelliJ can pick them up from there.
– Thilo
Nov 24 '18 at 9:31
I agree with this. All my IntelliJ projects use Maven or sbt and I don't check in any IntelliJ project files. All important settings are handled by Maven/sbt, and IntelliJ can pick them up from there.
– Thilo
Nov 24 '18 at 9:31
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53419030%2fwhich-idea-files-belong-in-version-control%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Easy way to find out: open up the file and see what's in it. If it's specific to your application, commit it.
– 3Dave
Nov 21 '18 at 19:14
1
@3Dave Not really. Most of them are specific to my application, but many of them are also specific to the current user, and some seem to be possible to delete entirely without any problem.
– rwallace
Nov 21 '18 at 19:17
Did you see this document?
– CrazyCoder
Nov 21 '18 at 19:54