Hm, I would recommend adding an .env.sample file in the repository. Instead of filling in the fields with real values, you can add placeholders, redactions, and "pseudo-values".
Then, of course, this would have to be documented and explained in the appropriate README.md.
Or perhaps, you could even forgo the .env.sample file and declare the environment variables in the README.md itself, but I personally prefer the former because it is more explicit.
# .env.sample
NODE_ENV=<production|development>
PORT=<open-port>
API_KEY=<github-key>
# And so on and so forth...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hm, I would recommend adding an
.env.samplefile in the repository. Instead of filling in the fields with real values, you can add placeholders, redactions, and "pseudo-values".Then, of course, this would have to be documented and explained in the appropriate
README.md.Or perhaps, you could even forgo the
.env.samplefile and declare the environment variables in theREADME.mditself, but I personally prefer the former because it is more explicit.