update .gitignore to ignore .env file

[rcraig14]

In the Quick Start guide one of the first steps is to make a new file called .env. The gitignore does not ignore this file. This can cause credentials to be leaked if accidentally pushed up

[vercel]

Someone is attempting to deploy a commit to the JS Mastery Pro Team on Vercel.

A member of the Team first needs to authorize it.

[spencerhunter]

@adrianhajdin , 👋 This peaked our interest @Dwolla. We noticed that people are leaking their Dwolla API credentials in a .env file that are getting pushed to public repositories. We're wondering if you could remove these API credentials as well as merge this PR to add .env* to .gitignore of this project? 🙏 Feel free to tag me if you have any questions on the Dwolla side!

[FaVstarr]

@adrianhajdin , 👋 This peaked our interest @Dwolla. We noticed that people are leaking their Dwolla API credentials in a .env file that are getting pushed to public repositories. We're wondering if you could remove these API credentials as well as merge this PR to add .env* to .gitignore of this project? 🙏 Feel free to tag me if you have any questions on the Dwolla side!

I noticed this earlier this week, that the .env wasn't added to the gitignore, luckily for me my repo isn't public, I later unlisted my .env from git them made all the necessary changes. Thanks for raising the concern.