Both rules were already present under "Visual C++ cache files", where they
have been since the template was created in 2010 (590e423). A second copy
was added in 2019 (e285e4b) under a new "Visual Studio 6 technical files"
heading, whose commit described them as "their purpose is unknown for me".
Beyond being duplicates, the second heading is inaccurate. Neither file is
specific to Visual Studio 6:
- *.ncb is the Visual C++ IntelliSense database, used through Visual Studio
2008 and replaced by the SDF database in 2010. The template already lists
*.sdf two lines below *.ncb in the "Visual C++ cache files" section, so
the pair belongs together there.
- *.aps is the binary form of the resource script used by the resource
editor. Microsoft documents it for msvc-140 through msvc-180 (Visual
Studio 2015 to 2022) and states plainly that it should not be in source
control.
The genuinely VS6-specific rules added by that commit (*.vbw, *.dsw, *.dsp)
are untouched. Behaviour is unchanged: both patterns are still ignored, once
each, under the heading that describes them correctly.
Since TwinCAT 3.1 build 4026.xx, the *.xtv file stores project-specific
mappings and must be tracked in version control. Only the backup and
temporary variants stay ignored.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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>
Claude Code creates git worktrees under .claude/worktrees/ at the repository
root. The official documentation explicitly recommends gitignoring this path
so worktree contents don't appear as untracked files in the main checkout.
Co-Authored-By: Claude Opus 5 <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
Adding a default `.gitignore` for new R projects is a nice features. Around 20% of CRAN packages contained compiled code, often C/C++ (and increasingly Rust etc). Those packages
will when `git add everything` is used also commit their object code and shared libraries. With this PR they will no longer so it should offer a small quality-of-life improvement to these repositories.
Devin Dooley