Created by: JimmyMcBride
I added yarn.lock, package-lock.json and .env to the git ignore for the base templates.
Yarn.lock and package-lock.json files are created during the npm/yarn install process, so they don't need to be uploaded. When they are uploaded they can not only cause annoying conflicts when working in a group on occasion but when left alone for a minute will cause GitHub to throw security warnings your way.
Having both of these files ignored also lets everybody on the team use their preference for npm or yarn without causing any hosting issues when trying to deploy.
Additionally, I have added the regular .env file to the git ignore. There are a few other types of .env files on the ignore, but not the vanilla .env file. Every time I add a .env file I end up accidentally uploading it to the repo and have to do some git magic to get it off again.