16 Commits
Author SHA1 Message Date
Russell Shean 80115b56bf Merge a614252a10 into e9c620b9f6 2026-04-06 22:49:56 +05:00
Devin Dooley e9c620b9f6 Merge pull request #4837 from haras-unicorn/feat-nix-ignore-nixos-test-history
feat(nix): ignore nixos test history
2026-04-06 09:43:23 -07:00
Devin Dooley 5853962226 Merge pull request #4826 from gxono/patch-1
TeX: add ConTeXt utility cache file (.tuc, .tui & tuo)
2026-04-06 09:41:52 -07:00
haras c5bf3caf29 feat(nix): ignore nixos test history 2026-04-06 18:38:27 +02:00
Devin Dooley 7514684825 Merge pull request #4835 from ysmartin/patch-1
Fix comment URL for Maven wrapper usage
2026-04-06 09:32:48 -07:00
Devin Dooley ad49657df2 Merge pull request #4836 from T1ckbase/fix/cpp-gitignore-whitespace
Remove trailing whitespace in C++.gitignore
2026-04-06 09:30:03 -07:00
T1ckbase 9ffced6030 Remove remaining trailing whitespace in C++.gitignore 2026-04-05 03:24:04 +08:00
T1ckbase 49990d1d63 Remove trailing whitespace in C++.gitignore 2026-04-05 03:15:27 +08:00
ysmartin 3d21cef359 Fix comment URL for Maven wrapper usage
Updated the URL and fragment in the comment for Maven wrapper usage.
2026-04-04 14:47:28 +02:00
Jonatán Perren de90107f1a TeX: add ConTeXt utility cache file (.tuc, .tui & tuo)
ConTeXt generates .tuc files (utility cache) during each run. 

These can be removed using the command line [--purgeall](https://wiki.contextgarden.net/Input_and_compilation/Executable_scripts_and_auxiliary_files/context_script#--purgeall).

ConTeXt MKII generates .tui and .tuo with the generation of [ToC](https://wiki.contextgarden.net/Document_structure_and_headlines/Table_of_contents).

These files store document metadata between compilations and are not part of the source, so they should be ignored.
2026-04-03 22:06:17 -03:00
Devin Dooley 84c6914a9b Merge pull request #4828 from quantum9Innovation/lean-gitignore
feat: create Lean.gitignore
2026-04-03 17:05:51 -07:00
Ananth VenkateshandDevin Dooley 5f760225cf fix: only match on .lake directory
Co-authored-by: Devin Dooley <dooleydevin@github.com>
2026-04-03 20:04:27 -04:00
Ananth Venkatesh b9ad512a45 feat: create Lean.gitignore 2026-03-28 21:42:41 -07:00
Jonatán Perren 9aa86b4610 TeX: add ConTeXt utility cache file (.tua & .tuc)
ConTeXt generates .tua and .tuc files (utility cache) during each run. These files store document metadata between compilations and are not part of the source, so they should be ignored.
2026-03-27 21:24:28 -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
6 changed files with 18 additions and 7 deletions

No files matched your search

+6 -6
View File
@@ -49,14 +49,14 @@ CMakeFiles/
CMakeCache.txt
cmake_install.cmake
Makefile
install_manifest.txt
install_manifest.txt
compile_commands.json
# Temporary files
*.tmp
*.log
*.bak
*.swp
*.tmp
*.log
*.bak
*.swp
# vcpkg
vcpkg_installed/
@@ -66,4 +66,4 @@ vcpkg_installed/
# test output & cache
Testing/
.cache/
.cache/
+2
View File
@@ -0,0 +1,2 @@
# cache and other artifacts produced by Lean's Lake build tool
.lake/
+1 -1
View File
@@ -7,7 +7,7 @@ release.properties
dependency-reduced-pom.xml
buildNumber.properties
.mvn/timing.properties
# https://maven.apache.org/wrapper/#usage-without-binary-jar
# https://maven.apache.org/tools/wrapper/#Usage_with_or_without_Binary_JAR
.mvn/wrapper/maven-wrapper.jar
# Eclipse m2e generated files
+3
View File
@@ -4,3 +4,6 @@ result-*
# Ignore automatically generated direnv output
.direnv
# Ignore NixOS interactive test driver history
**/.nixos-test-history
+1
View File
@@ -38,6 +38,7 @@ vignettes/*.pdf
# R Environment Variables
.Renviron
.env
# pkgdown site
docs/
+5
View File
@@ -75,6 +75,11 @@ acs-*.bib
# comment
*.cut
# context
*.tuc
*.tui
*.tuo
# cprotect
*.cpt