Compare commits

...

8 Commits

Author SHA1 Message Date
Russell Shean
c3318530cb
Merge a614252a10 into 1046d8fba6 2026-04-27 20:01:10 +00:00
Devin Dooley
1046d8fba6
Merge pull request #4846 from yufeiminds/main
Add .gitignore for MoonBit
2026-04-27 09:16:09 -07:00
Yufei Li
b632b12ac9 fix: Fix comment style issues 2026-04-27 15:21:45 +08:00
Yufei LI
47eaa84be9 fix: Remove bin 2026-04-20 01:14:53 +08:00
Yufei LI
4a96a23dfd fix: Remove deprecated folder and logs 2026-04-20 01:01:50 +08:00
Yufei LI
071d8034a4 Add .gitignore for MoonBit 2026-04-20 00:31:16 +08: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
2 changed files with 54 additions and 0 deletions

53
MoonBit.gitignore Normal file
View File

@ -0,0 +1,53 @@
# Build System Artifacts
# MoonBit default build output directory.
_build/
# Local MoonBit package cache directory.
.mooncakes/
# Coverage and Test Artifacts
# Coverage reports generated by MoonBit tooling.
moonbit-coverage-*.txt
# Coverage output directory used by coverage commands.
_coverage/
# Bisect runtime coverage data file.
bisect.coverage
# JavaScript Target Artifacts
# Uncomment if generated JavaScript should be ignored.
# *.js
# Source map files generated for JavaScript output.
*.js.map
# Node.js dependencies used in JS target workflows.
node_modules/
# WebAssembly Target Artifacts
# Compiled WebAssembly binaries.
*.wasm
# WebAssembly text format output.
*.wat
# MoonBit Pilot / Agent Artifacts
# MoonBit agent runtime state and temporary files.
.moonagent/
# LLVM Backend Artifacts
# LLVM textual intermediate representation (IR) files.
*.ll
# LLVM bitcode files.
*.bc
# Native object files from LLVM/native compilation.
*.o
# Generated assembly source files.
*.s
# Default executable output name on Unix-like systems.
*.out
# Native executable output on Windows.
*.exe
# macOS debug symbol bundles.
*.dSYM/

View File

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