7 Commits
Author SHA1 Message Date
Russell Shean bbf3d47024 Merge a614252a10 into 32652622a4 2026-08-25 19:15:51 +02:00
Devin Dooley 32652622a4 Merge pull request #4741 from sundowatch/julia
Julia: ignore *.jl.*.mem and CondaPkg's project-local environment
2026-08-25 10:02:49 -07:00
ibrahimandClaude Opus 5 8f80fc38c9 Julia: ignore *.jl.*.mem and CondaPkg's project-local environment
Replaces the previous contents of this branch, which added editor/OS and
shared-library rules that belong in Global/ per the contributing guidelines.

Two changes remain, both scoped to Julia.gitignore:

* `*.jl.*.mem` — `--track-allocation` writes `<file>.jl.<pid>.mem`, so the
  existing `*.jl.mem` rule never matches the files Julia actually produces.
  This mirrors the `--code-coverage` section, which already carries both
  `*.jl.cov` and `*.jl.*.cov`.

* `.CondaPkg/` — CondaPkg creates this directory inside the active project
  and populates it with a machine-specific Conda environment.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-25 08:20:34 +03: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
ibrahim 40c5d3211c remove __pycache__. Because this pattern is Python-specific; remove .julia_history. Because The .julia_history pattern is redundant since .history would already match it 2025-10-04 09:04:10 +03:00
ibrahim d8635c69ba Add ignore rules for Revise package files and common editor/OS temporary files in Julia projects 2025-10-04 08:53:35 +03:00
2 changed files with 5 additions and 0 deletions

No files matched your search

+4
View File
@@ -4,6 +4,7 @@
# Files generated by invoking Julia with --track-allocation
*.jl.mem
*.jl.*.mem
# System-specific files and directories generated by the BinaryProvider and BinDeps packages
# They contain absolute paths specific to the host computer, and so should not be committed
@@ -26,3 +27,6 @@ Manifest*.toml
# File generated by the Preferences package to store local preferences
LocalPreferences.toml
JuliaLocalPreferences.toml
# Conda environment and metadata created in the project directory by the CondaPkg package
.CondaPkg/
+1
View File
@@ -38,6 +38,7 @@ vignettes/*.pdf
# R Environment Variables
.Renviron
.env
# pkgdown site
docs/