.idea/*
!.idea/codeStyles
!.idea/runConfigurations

.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json
!.vscode/*.code-snippets

Note: I haven't checked the vs code ones in depth, the list might not be perfect.

[–] kora@sh.itjust.works 14 points 2 days ago* (last edited 2 days ago) (8 children)

I personally strongly advise against committing IDE junk to version control. Assuming your IDE workspace defaults are "sane" for the rest of the contributors is not a good practice.

[–] JackbyDev@programming.dev 2 points 2 days ago (4 children)

If your whole team uses the same IDE, what's wrong with commiting things like run configurations and code styles? I agree in general, but a wholesale ban on it is very cargo culty to me. There can be legitimate times to do it.

[–] kora@sh.itjust.works 5 points 2 days ago

I elaborated on it below. Your team will grow and shrink. No guarantee that each developer will bring the same IDE. This is especially true for open source projects.

If it works your team, no need to be dogmatic about it. Just be careful about what you put there and agree on a set of sane defaults with your team. Your project should build and run tasks without needing a specific IDE.

load more comments (3 replies)

load more comments (6 replies)

load more comments (12 replies)