Include other editors than JetBrains in the .gitignore

[springdo]

Hello,

I would like to include some other editors such as Eclipse in the workspace exclude for the .gitignore.
Happy to PR if you feel appropriate

[vpanjganj]

Yes, please go ahead, thanks.

[bluepeter]

Honestly, the .gitignore is some kinda of crazy... why such an elaborate one? These are things that should be configured on a case by case basis... and really, many of these feel as though they belong in user dir, vs project dir.

[bluepeter]

A ~600 line default .gitignore is just asking for trouble... and is going to scare off new users from editing it to tune to constantly changing needs.

[vpanjganj]

@bluepeter What do you suggest? Maybe we can promote one of these .gitignore generator tools?

[bluepeter]

I'm not sure, but this feels honestly counterproductive. Some people will assume this is the "default" and go with it. As a result, they will get something completely counterproductive such as:

### Web ###
  | *.asp
  | *.cer
  | *.csr
  | *.css
  | *.htm
  | *.html
  | *.js
  | *.jsp
  | *.php
  | *.rss
  | *.xhtml

... which I can't ever imagine every being useful?

I'd honestly scrap it. It requires too much configuration. Havent' looked at any of the generators. Perhaps, instead, give some common-sense advice on rationale behind .gitignore strategies... e.g., why they shouldn't check-in node-modules/ etc.

[springdo]

It is very unweildy at the moment the .gitignore - perhaps the suggestion here is not to include ALL of this as what you'd include in your project but examples for common project types? Or groupings for tech types? It's always handy having a gitignore to hand when starting a new project

[antony]

@bluepeter is right. keep your IDE ignores on your machine. Nobody needs to ignore an enitre IntellIJ IDEA file-based project structure when they use tmux+vim for development.

Best to keep .gitignore focussed on global ignores specific to the project.

[vpanjganj]

The reason I put editors in there was based on my own experience. I had to delete someone else's .idea folder from repos.

[antony]

@vpanjganj and I absolutely have experienced the same thing - but rather than pollute .gitignore I think this scenario is a good time to educate other collaborators about the ability to have a local set of .gitignores for such things. It comes down to discipline, much like following a set of project guidelines like this :)

[yeskunall]

I see the need to ignore .idea and other files and folders generated by IDEs to manage project settings, but what about cases where pushing those configurations is encouraged, for example, in the case of people using vscode? In that case, it makes sense to push .vscode to enhance the developer environment.

A ~600 line default .gitignore is just asking for trouble

I actually agree with @bluepeter on this one. From what I understand, that .gitignore was created by pulling the data from gitignore.io, so I'd like to make a suggestion:

Maybe we can expand on the section for .gitignores. We can start by mentioning that the .gitignore for a specific project varies greatly based on the development environment (editors, IDEs, OS) and the technologies used in that project. (Node, Go, PHP, etcetera) Keeping that in mind, we can break that large .gitignore file into smaller chunks and point to the different .gitignores according to the project needs and requirements.

Thoughts?

[skyrpex]

I would just add rules to the gitignore that are related to the project, not the editor. For example, node_modules and .log files. Other things should be globally ignored by the user.

[vpanjganj]

in the case of people using vscode?

I think the current config for vscode handles that. You most likely want to push tasks.json etc...

### VisualStudioCode ###
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json

A ~600 line default .gitignore is just asking for trouble

I agree with that as well, I think this file should be trimmed down.

Go, PHP, etcetera, Keeping that in mind

I think we stick to be guidelines for JavaScript projects for now and do it right, this also prevents the docs from getting enormous.

My suggestion is:

• Adding the major Javascript IDEs (how many are they 5? 6?)
• Adding default OS files that we usually add to .gitignore,
• node,javascript usuals (node_modules, *.log, etc...)

[vpanjganj]

@skyrpex

Other things should be globally ignored by the user.

You know what, I think you're right.
In that case we can have a small description on how each developer should set a global .gitignore and then as you said, add the usual ones (node_modules etc...)