First, does .env.development have any effect on the live project if it's included in the GH repo? I believe it doesn't but looking for confirmation.

Second, isn't it generally the case that the .env files should not be added to git? Esp if they contain secrets - and typically people do add them here for third part services etc. Yes, they'd be local secrets but that could still be a concern for any third part systems being used.

So I'm wondering whether the code here should include .env.development in .gitignore by default since CLI writes the initial file - and whether I should ignore it myself at this point.

https://github.com/nhost/cli/blob/a23f8ceebf2d87f932559d4bce0570fe59da68d3/cmd/init.go#L223

> First, does .env.development have any effect on the live project if it's included in the GH repo?
No

Generally .env* files should be ignored yes