So….if you want to have environmental variables, you’ll create the .env file right? Well…what if you want to share a repo with team members? Do they have to each manually create a .env file when working on the repository locally or is there a better solution than that? I’m just trying to think of the security behind not allowing everyone to have access to the private strings in a .env file but be able to use the repo as if there was a .env file.
I’m hosting my code in GitHub for reference. Is this a GitHub actions thing or is there another solution? Any help would earn my eternal gratitude in this dire time, lol
There is this Stack Overflow thread that is similar, but I don't want the environmental variables for deployment, just for team-members to do a git-pull and get the repository to work locally without needing to custom-create the .env file and add in the environmental variable strings: React app build/deploy using github actions with secrets