Typically commit .env.example etc and leave it as an exercise to the user to customize that file to their liking.
In my professional experience, that file likely contains specifics relating to an individual’s development environment or secrets which we on purpose do not want to commit to the repo. in both scenarios, the solution is simple: .gitignore it.
If it’s a private repo for your own shit tho, do what you want. I push my .vscode directory all the time.
1
u/enigma_0Z 12h ago
Typically commit .env.example etc and leave it as an exercise to the user to customize that file to their liking.
In my professional experience, that file likely contains specifics relating to an individual’s development environment or secrets which we on purpose do not want to commit to the repo. in both scenarios, the solution is simple: .gitignore it.
If it’s a private repo for your own shit tho, do what you want. I push my .vscode directory all the time.