tworu/gitignore
1
0
Fork 0
mirror of https://github.com/github/gitignore.git synced 2026-08-28 18:57:20 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

Compare commits

base: tworu:c3318530cba00a4d8e75d8ab9de0ba4617b588ad
Branches Tags
tworu:main
tworu:remove-duplicate-template
tworu:copilot/research-github-gitignore-repository
tworu:copilot/research-global-macos-gitignore
tworu:copilot/research-pr-4811
tworu:copilot/research-pr-4811-analysis
tworu:rmw-universe
tworu:rmw-universe-2022
tworu:annotating-visualstudio
tworu:add-metadata
tworu:ghfw
tworu:reduce-noise
tworu:old-ghfw
...
compare: tworu:f4684bdca700caef591730332eee47e14529ae59
Branches Tags
tworu:main
tworu:remove-duplicate-template
tworu:copilot/research-github-gitignore-repository
tworu:copilot/research-global-macos-gitignore
tworu:copilot/research-pr-4811
tworu:copilot/research-pr-4811-analysis
tworu:rmw-universe
tworu:rmw-universe-2022
tworu:annotating-visualstudio
tworu:add-metadata
tworu:ghfw
tworu:reduce-noise
tworu:old-ghfw

3 Commits
c3318530cb ... f4684bdca7

Author SHA1 Message Date
Russell Shean
f4684bdca7
Merge a614252a10 into 5763345204 2026-04-25 10:00:10 +09:00
Russell Shean
a614252a10
Merge pull request #1 from Russell-Shean/Russell-Shean-patch-1 
R: add `.env` to prevent accidentally exposing credentials
 2025-12-19 19:30:56 +08:00
Russell Shean
460b9d97a7
R: add .env to prevent accidentally exposing credentials 
Historically R users have used the .Renviron file for storing environmental variables such as secrets, credentials, API keys etc. However, I believe there are several compelling reasons for adding .env to the .gitignore too:

1. The dotenv R package was created to allow users to use .env instead of .Renviron. The package has a significant number of downloads.  https://github.com/gaborcsardi/dotenv 

2. .env files are standard in many other programming languages. It wouldn't be that out of the unexpected to think R users might end up with an .env file because a python user on their team contributed files to the repo, the R user started programming in nodejs and is used to working with .env file, or a repo is in the process of being translated from a language that uses .env to R. 

3. LLMs are making programming accessible to people who may not have much previous experience handling credentials and security. One of the first steps many of these users have to do is store LLM provider API keys somewhere. I worry about a new R user adapting a python workflow or an R workflow that recommends using an .env file and then accidentally committing their LLM API keys to a public repo. 

4. I can't think of why an R user would create an .env file for any other reason other than storing credentials and environmental variables. If, for whatever reason, they need to commit an .env file, they can remove that part from the template, but I think the risk of accidentally exposing sensitive credentials justifies adding .env files to the template and not commenting it out by default.
 2025-12-19 19:27:15 +08:00
1 changed files with 1 additions and 0 deletions
Show Stats Expand all files Collapse all files

1
R.gitignore
View File

@ -38,6 +38,7 @@ vignettes/*.pdf
# R Environment Variables
.Renviron
.env
# pkgdown site
docs/