Add .env to generated .gitignore file

[nolawnchairs]

Is there an existing issue that is already proposing this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe it

Not related to a problem.

Describe the solution you'd like

The auto-generated .gitignore file ought to have .env included by default.

Teachability, documentation, adoption, migration strategy

No response

What is the motivation / use case for changing the behavior?

The .env file is a common file in many projects that holds configuration data and secrets that oughtn't be checked into version control.

[kamilmysliwiec]

Would you like to create a PR to address this issue?

[micalevisk]

@nolawnchairs you just need to change this: https://github.com/nestjs/nest-cli/blob/2271c9e0ba6be1c7a202ef1b67d81407a0ac26d5/lib/configuration/defaults.ts#L21 😸

---

@kamilmysliwiec this is at nest-cli side because somewhat .gitignore files aren't published to NPM, see https://github.com/nestjs/nest-cli/blob/6ce99a06152a12c9eeb483aaae3889fe0d48c327/actions/new.action.ts#L193-L196

[micalevisk]

actually, this is already done. See:

schematics/src/lib/application/files/js/.gitignore

Lines 3 to 4 in 93762c3

	# project files
	.env

schematics/src/lib/application/files/ts/.gitignore

Lines 3 to 4 in 93762c3

	# project files
	.env

We just need to wait for the fix commented here: nestjs/nest-cli#1630 (comment) so nest new could generate those .gitignore