gitignore and vscode folder | Official Unity Discord | Page 1

barren salmon Mar 7, 2026, 2:41 PM

#

Hello, might be a stupid question.
About .gitignore, how should we treat .vscode/ and .idea/ folders (IDE specific files)? Is there standard answers?

I use Unity.gitignore from GitHub/gitignore repo as default, but there's no clue about them.
I know the brute-force answer is to just ignore them, and I guess many people do like this.
Another people says there are something need to be shared, since they are not cache folder like .vs/ but workspace settings, e.g. .vscode/launch.json.
I want to see if there's any "standard" or "default" answer or other insight, like side effects or something else.

copper whale Mar 7, 2026, 2:45 PM

#

If you're working with other people, add them to the ignore.

If you're working solo on multiple machines, do whatever you want, keep or ignore.

barren salmon Mar 7, 2026, 2:57 PM

#

Yes, I'm in the context of working with other people.
But there are other response saying they are "workspace folder" or "have its usage". Like these:

https://github.com/github/gitignore/pull/4546
https://github.com/github/gitignore/pull/4516
I also heard similar statement in other random place.
So I guess I need some powerful statement, to point out whether to ignore or not.

runic canopy Mar 7, 2026, 3:00 PM

#

The fact that you're seeing multiple different opinions should be a clue that it's a matter of opinion/preference and there is no universal truth that you could find that tells you what to do

#

If you want to enforce the same settings for all team members, include the folders in the repo. Usually people use their personal settings and would find that annoying.

#

Some teams make macros and shortcuts and want them to be shared

barren salmon Mar 7, 2026, 3:11 PM

#

Since I always stay in small/medium studio, I always just ignore those folder, since there're always something changing. But I really don't know what happened in bigger teams. My experience does not give me enough confident for this question.
Maybe I should ask from another aspect:
Did anyone meet the actual case that need to upload them to Git?

copper whale Mar 7, 2026, 3:13 PM

#

Nitku already gave you examples of why it would be shared.

runic canopy Mar 7, 2026, 3:17 PM

#

Also "share things like launch configurations" from one of the linked Github issues. Bigger teams might have that kind of custom workflows

barren salmon Mar 7, 2026, 3:18 PM

#

I see....I'm swallowing the "no universal truth" part.
Thanks guys!

runic canopy Mar 7, 2026, 3:21 PM

#

A good rule of thumb is that if you don't have a reason to include them in the repo, start with not sharing them. If you later do need to do that it's just a matter of removing one line from gitignore

#gitignore and vscode folder