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>
- The “Builds” folder pattern would match source code files starting
with “Builds”. Corrected to only match directories with Xojo’s
Builds folder naming convention.
- Removed blank line between comment heading and patterns
Keep only documented local/high-churn agent artifacts active by default, preserving common shared instruction/config files as commented opt-in examples
As of Godot 4.2 the editor has a Windows-specific workaround for loading extension libraries.
Before the extension library is loaded the Godot editor creates a temp copy of the extension library `.dll` file with a `~` prefix (e.g. `example.dll` => `~example.dll`).
When the extension library is unloaded the Godot editor deletes the temp copy.
These copied `~*.dll` files are temporary and should be ignored.
References:
Godot 4.2 changelog
https://godotengine.org/article/godot-4-2-arrives-in-style/#gdextension
Godot PR #80188 GDExtension: Copy DLL to a temp file before opening
https://github.com/godotengine/godot/pull/80188
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.
/UIElementsSchema is an auto-generated folder created by Unity. It is used in the UI Toolkit.
In Unity discussions, staff have confirmed that this folder can be safely ignored.
https://discussions.unity.com/t/uielementsschema/805120
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Nathan C.