From 5a0080ce6e33ac2b1b93483d85e20d08c9915b44 Mon Sep 17 00:00:00 2001 From: Antoine Zambelli Date: Sun, 31 May 2026 17:48:18 -0500 Subject: [PATCH] chore: generalize eval-results LFS rule to catch versioned dumps The two LFS patterns matched only 'eval_results.jsonl' and the now-dead rig-tagged 'eval_results_rig*.jsonl' naming. The current scheme is version-tagged ('eval_results_v0.7.0.jsonl'), which neither pattern matched -- git check-attr reported 'unspecified' for those files, so the next release dump (eval_results_v0.7.3.jsonl) would have committed as a plain ~67MB git blob instead of an LFS pointer. Collapse both into one glob 'eval_results*.jsonl' covering bare, rig-tagged, and version-tagged variants. Existing v-file pointers are unchanged; this only closes the gap for future dumps. --- .gitattributes | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.gitattributes b/.gitattributes index 9b02730..8b9528d 100644 --- a/.gitattributes +++ b/.gitattributes @@ -5,5 +5,5 @@ *.toml text eol=lf *.yml text eol=lf *.yaml text eol=lf -eval_results.jsonl filter=lfs diff=lfs merge=lfs -text -eval_results_rig*.jsonl filter=lfs diff=lfs merge=lfs -text +# Eval result dumps (any variant: bare, rig-tagged, version-tagged) go to LFS. +eval_results*.jsonl filter=lfs diff=lfs merge=lfs -text