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







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,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














  • 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

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














  • 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







-

這個網誌中的熱門文章

Tangent Lines Diagram Along Smooth Curve

圖片
7 1 I am trying to replicate a diagram and have a minimal example. I don't know how to add additional tangents between the specified points and preserve smoothness. documentclass{article} usepackage{tikz} usetikzlibrary{calc,intersections} begin{document} begin{tikzpicture} % Axes draw [->, name path=x] (-1,0) -- (11,0) node [right] {$x$}; draw [->] (0,-1) -- (0,6) node [above] {$y$}; % Origin node at (0,0) [below left] {$0$}; % Points coordinate (start) at (1,-0.8); coordinate (c1) at (3,3); coordinate (c2) at (5.5,1.5); coordinate (c3) at (8,4); coordinate (end) at (10.5,-0.8); % show the points foreach n in {start,c1,c2,c3,end} fill [black] (n) circle (2pt) node [below] {}; % join the coordinates draw [thick,name path=curve] (start) to[out=70,in=180] (c1) to[out=0,in=180]
閱讀完整內容

Yusuf al-Mu'taman ibn Hud

圖片
Main article: Taifa of Zaragoza Al-Mu'taman Ruler of Zaragoza Reign 1081–1085 Predecessor Ahmad al-Muqtadir Successor Al-Mustain II Born Zaragoza Died 1085 Full name Yusuf ibn Ahmad al-Mu'taman ibn Hūd House Banu Hud Yusuf ibn Ahmad al-Mu'taman ibn Hūd (Arabic: المؤتمن بالله يوسف إبن أحمد إبن هود ‎, al-Mutaman bi l-Lah , died c. 1085) was the third king of the Banu Hud dynasty who ruled over the Taifa of Zaragoza from 1081 to 1085. Yusuf al-Mutaman reigned during the height of power of Muslim Zaragoza , following the thriving period of his father Ahmad al-Muqtadir. He continued his father's efforts and created around him a court of intellectuals, living in the beautiful palace of Aljafería, nicknamed as "the palace of joy". Al-Mu'taman was also a scholarly king and a patron of science, philosophy and arts. As an example of a wise king, he knew astrology, philosophy, and especially mathematics, a discipline in which
閱讀完整內容

Zucchini

圖片
This article is about the vegetable. For other uses, see Zucchini (disambiguation). Zucchini (courgette) A striped and a uniform color zucchini Genus Cucurbita Species Cucurbita pepo Origin 19th century northern Italy The zucchini ( / z uː ˈ k iː n i / , American English) or courgette ( / k ʊər ˈ ʒ ɛ t / , British English) is a summer squash which can reach nearly 1 metre (100 cm; 39 in) in length, but is usually harvested when still immature at about 15 to 25 cm (6 to 10 in). [1] A zucchini is a thin-skinned cultivar of what in Britain and Ireland is referred to as a marrow. [2] [3] In South Africa, a zucchini is known as a baby marrow. Along with certain other squashes and pumpkins, the zucchini belongs to the species Cucurbita pepo . It can be dark or light green. A related hybrid, the golden zucchini, is a deep yellow or orange color. [4] In a culinary context, the zucchini is treated as a vegetable; it is usually cooked and presented as a savory dish o
閱讀完整內容