DEV Community

Discussion on: Please don't commit .env

Collapse
 
bgadrian profile image
Adrian B.G.

Nope, thats what they say but is it a bad practice.

Each env had its own tweaks and sometimes diffenrent platforms, tasks, settings and folders. Each dev should have the liberty of using its own IDE in their own productive way.

Thread Thread
 
snowe2010 profile image
Tyler Thrailkill

Ah yes, let's not use the tool as instructed. That will go great.

Each env had its own tweaks and sometimes diffenrent platforms, tasks, settings and folders. Each dev should have the liberty of using its own IDE in their own productive way.

Yeah, and they tell you exactly which things to exclude in order to get that.

You should include the idea folder. End of story.

Thread Thread
 
bgadrian profile image
Adrian B.G.

No, sorry.

Do some research on the topic you will see that many other developers share my opinion. Do not blindly trust the IDE creators, for them is a business, for you is just a tool.

IDE's are local tools, they are not related to the project. A big project then will have

.vim
.idea
.eclipse
.atom
.vscode

folders. Where did you saw that?

You can also browse popular open source projects source code and see that most of them do not have IDE config files.

Thread Thread
 
dietergeerts profile image
Dieter Geerts

That's because devs want "clean" repos, but there is a JetBrains template, which will ignore USER settings, but you should still commit PROJECT setttings, as not all settings can be read from .editorconfig or linting etc.... This will help other devs that uses that IDE to not waste time on configuring the IDE to get auto-format correct etc... Also VSCode has files that should be committed.