Which IDEA files belong in version control?












3















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







share|improve this question


















  • 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
















3















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







share|improve this question


















  • 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














3












3








3








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







share|improve this question














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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 '18 at 19:10









rwallacerwallace

9,4702173147




9,4702173147








  • 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





    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












1 Answer
1






active

oldest

votes


















2














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.






share|improve this answer



















  • 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











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
});


}
});














draft saved

draft discarded


















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









2














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.






share|improve this answer



















  • 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














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.






share|improve this answer



















  • 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








2







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.






share|improve this answer













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.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 24 '18 at 9:18









FrankieFrankie

18.8k1060104




18.8k1060104








  • 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





    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




















draft saved

draft discarded




















































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.




draft saved


draft discarded














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





















































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







-

Popular posts from this blog

"Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

Image
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 2 total noob sorry any help greatly appreciated. I keep getting this "Incorrect syntax near the keyword 'ON'." heres my codes code one CREATE TABLE supplier ( supplierID INT PRIMARY KEY, ISBN INT FOREIGN KEY REFERENCES book(ISBN), price DECIMAL (5,2), ON UPDATE CASCADE, ON DELETE CASCADE, ); code two CREATE TABLE orders ( orderID INT PRIMARY KEY, customerID INT FOREIGN KEY REFERENCES customer(customerID), ISBN INT FOREIGN KEY REFERENCES book(ISBN), orderDate date, ON UPDATE CASCADE, ON DELETE CASCADE, ); Ive run out of stuff to try other than dumbing it down to uselessness. ...
Read more

Alcedinidae

Image
Alcedinidae Martin-pêcheur à dos bleu ( Alcedo azurea ) Classification (COI) Règne Animalia Embranchement Chordata Sous-embr. Vertebrata Classe Aves Ordre Coraciiformes Famille Alcedinidae Rafinesque, 1815 Les Alcédinidés ou Alcedinidae forment une famille d'oiseaux plus connus sous les noms de martins-pêcheurs et martins-chasseurs. Sommaire 1 Description 2 Répartition et habitat 3 Systématique 3.1 Liste alphabétique des genres 3.2 Liste des espèces 4 Chez les Anciens : l'alcyon 4.1 Étymologie (Littré) 4.2 Oiseau « fabuleux » ? 5 Notes 6 Articles connexes 7 Liens externes 7.1 Bibliographie Description | Ce sont des oiseaux compacts de taille petite à moyenne (10 à 46 cm), au bec droit et long, en forme de poignard. Leurs pattes sont courtes, et ils portent un plumage aux couleurs vives. Répartition et habitat | Cosmopolites, ils fréquentent surtout ...
Read more

Origin of the phrase “under your belt”?

Image
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0; } 17 1 Today, I found myself discussing what students should have "under their belts" during a lecture, and I wondered to myself if there was some inappropriate undertone here that I might be unaware of. Question : What is the origin of the phrase "under your belt"? A google search revealed some webpages (e.g. [1]) that assert its origin is related to consumption of food -- once a meal has been eaten, it's under your belt (which is a relief). However, with such websites, I have no way to determine fact from "random guy on the internet making stuff up". etymology idioms ...
Read more