zeekayandHanzo Dev f236b2a7d8 Untrack the cargo build output, and ignore it where it actually lives ...

86 MB across 298 files — the fingerprint cache, the per-machine
.cargo-lock files, a macOS dylib and a macOS-arm64 wheel — rode in on a
commit about documentation wording. Nothing reads any of it; the crate
builds from source everywhere.

The ignore rules meant to stop this could not. `target/*` and
`rust/target/` both carry a slash before the end, which anchors them to
this file's directory, and the files were under
rust/insightsql/parser/target/ — a path neither one names. One
unanchored `target/` matches a cargo output directory at any depth, so
the next crate to appear somewhere new is covered without editing this
file again.

A pattern only decides what git offers to add, never what it is already
tracking, so the rule alone would have changed nothing here: the 298
files stay tracked until they are removed from the index, which is the
other half of this commit. They remain on disk.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-22 19:34:58 -07:00

..

parser

Untrack the cargo build output, and ignore it where it actually lives

2026-08-22 19:34:58 -07:00