-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.gitignore in default starter does not work for .env.development, .env.production, etc. files #18967
Comments
What does your |
Hey @bvlktech - Thanks for your reply! Yes, I can manually change the I was just thinking that that line should be changed in the repo though, so that anybody who uses the starters doesn't have to add the |
what starter are u using the default one? |
@bvlktech Yes, I typically use the default starter on my projects. Although on that PR, @pieh asked me to update the |
well the default one is made / maintaind by gatsby itsself where as the other starters are by other devs i can change the .gitignore in the def starter but the others are up to those devs if they want to implament it ill also ref this as a discussion so this gets known about |
Description
When I create a new Gasby site using the Default Starter, then add environment variable files other than
.env
, such as.env.deveolopment
or.env.production
, they are not git ignored.Steps to reproduce
Create a new Gasby site using the Default Starter and add a environment variables file other than
.env
, such as.env.deveolopment
or.env.production
, then rungit status
to confirm that it is not being git ignored.Expected result
Environment variable files such as
.env.deveolopment
and.env.production
should be git ignored.Actual result
Environment variable files such as
.env.deveolopment
and.env.production
are not git ignored.Environment
System:
OS: macOS 10.14.6
CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Shell: 5.3 - /bin/zsh
Binaries:
Node: 12.3.1 - /usr/local/bin/node
npm: 6.9.0 - /usr/local/bin/npm
Languages:
Python: 2.7.10 - /usr/bin/python
Browsers:
Chrome: 78.0.3904.70
Firefox: 69.0.3
Safari: 13.0.2
npmGlobalPackages:
gatsby-cli: 2.8.5
gatsby: 2.10.0
The text was updated successfully, but these errors were encountered: