Merge 53c17f3bac into 9e86bc12f6

Merge pull request #4908 from ssmurfgg04-gif/fix-inforcrm-link
Update InforCRM.gitignore website link
2026-11-01 15:42:39 +01:00 · 2026-09-09 08:42:52 -04:00 · 2026-09-08 10:21:58 -07:00 · 2026-09-06 22:37:06 +03:00 · 2026-09-04 16:07:57 -07:00 · 2026-09-04 15:46:48 -07:00
5 changed files with 10 additions and 2 deletions
@@ -15,3 +15,4 @@
 *.aliases
 *.lvlps
 .cache/
 *.UserState
@@ -83,6 +83,9 @@ out
 dist
 .output
 # NitroJS
 .nitro/
 # Gatsby files
 .cache/
 # Comment in the public line in if your project uses Gatsby and not Next.js
@@ -122,7 +125,7 @@ dist
 # TernJS port file
 .tern-port
-# Stores VSCode versions used for testing VSCode extensions
+# Stores Visual Studio Code versions used for testing Visual Studio Code extensions
 .vscode-test
 # pnpm
@@ -38,6 +38,7 @@ vignettes/*.pdf
 # R Environment Variables
 .Renviron
 .env
 # pkgdown site
 docs/
@@ -95,7 +95,7 @@ For example, this template might live at `community/DotNet/InforCRM.gitignore`:
 ```gitignore
 # gitignore template for InforCRM (formerly SalesLogix)
-# website: https://www.infor.com/product-summary/cx/infor-crm/
+# website: https://www.infor.com/products/customer-experience-suite/crm
 #
 # Recommended: VisualStudio.gitignore
@@ -427,3 +427,6 @@ FodyWeavers.xsd
 *.msix
 *.msm
 *.msp
 # Official VS Code C# Dev Kit Extension exclusion
 #*.lscache
Author	SHA1	Message	Date
Sonik Bariya	2f2def3493	Merge `53c17f3bac` into `9e86bc12f6`	2026-09-09 08:42:52 -04:00
Devin Dooley	9e86bc12f6	Merge pull request #4908 from ssmurfgg04-gif/fix-inforcrm-link Update InforCRM.gitignore website link	2026-09-08 10:21:58 -07:00
ssmurfgg04-gif	7ee2cb86a4	docs: update dead Infor CRM website link	2026-09-06 22:37:06 +03:00
Devin Dooley	361f1e6afa	Merge pull request #4839 from wherewhere/lscache Add *.lscache to VisualStudio.gitignore	2026-09-04 16:07:57 -07:00
Devin Dooley	47cf7a7ff9	Merge pull request #4800 from crossrulz/patch-1 Add UserState folder to LabVIEW.gitignore	2026-09-04 15:46:48 -07:00
Devin Dooley	f5de2c2bb2	Merge pull request #4773 from Zamiell/fix-style fix: incorrect stylization of VS Code	2026-09-04 15:28:05 -07:00
Devin Dooley	110ac8d876	Merge pull request #4772 from Russell-Shean/main R: add .env to prevent accidentally exposing credentials	2026-09-04 15:22:03 -07:00
where whereandFrulfump	a11ba2154c	Fixed typo Co-authored-by: Frulfump <Frulfump@users.noreply.github.com>	2026-06-12 00:43:02 +08:00
where where	038ca52c7c	Use the comment in .NET SDK	2026-06-11 11:38:40 +08:00
where where	ce9cf62da7	Comment out lscache entry in gitignore	2026-05-16 12:59:41 +08:00
where where	18b5ee4870	Add *.lscache to VisualStudio.gitignore	2026-04-07 16:29:41 +08:00
Sonik Bariya	53c17f3bac	Add .nitro for nitrojs	2026-02-21 21:11:54 +05:30
Tim Robinson	f81300fe73	Add UserState folder to LabVIEW.gitignore	2026-02-19 09:30:21 -05:00
Zamiell	dfa24bf510	fix: incorrect stylization of VS Code	2025-12-21 12:13:30 -05: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