From 4c918a4879463ccf8748d18707c6f998f9872b29 Mon Sep 17 00:00:00 2001 From: bong-water-water-bong Date: Sun, 8 Nov 2026 19:01:22 -0400 Subject: [PATCH] gitignore: HRX probe run output, so the copyright gate stops reading the working tree as the repo tools/copyright.py lists tracked files UNION untracked-but-not-ignored files - deliberately, because its own comment says the check runs "before `git add`, so the check would report green on the file most likely to be missing its notice". .hrx123/logs/*.jsonl are untracked probe output with no comment syntax, so any developer clone that has run a probe reds the gate on files that are not in the repository: no comment style known (add one to LINE_STYLES/BLOCK_STYLES or EXEMPT): .hrx123/logs/probe-dumpcheck.jsonl That is a red that is the tree's, not the repo's, and this is the gate that caught base-modes-keep's duplicated licence block within two hours of being written (engine#1551 -> engine#1560) - the cheapest way to lose that is to teach people the gate is noisy. Ignoring the run-output path fixes it at the listing rather than by exempting files inside the checker, so the deliberate untracked-source behaviour is untouched, and it also stops run output being committed by accident. Measured on a clean checkout of main, same tree, same untracked file: before: python3 tools/copyright.py --check -> rc 1 "no comment style known ...: .hrx123/logs/probe-dumpcheck.jsonl" after: python3 tools/copyright.py --check -> rc 0 (that file still present) guard: an untracked SOURCE file with no notice still reds: "missing copyright notice: zz-untracked-guard.sh" -> rc 1 Fixes #1564 --- .gitignore | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.gitignore b/.gitignore index 08fc0ad18..7925b4d1d 100644 --- a/.gitignore +++ b/.gitignore @@ -34,3 +34,10 @@ third_party/toolchain/ # the model-pin sweep writes these where it runs (tools/pin_watch.py --check --json) pin-report.md pin-report.json + +# HRX probe run output: the .hrx123 probe tools write JSONL logs here. Run output is not source and carries no +# licence notice, but tools/copyright.py deliberately also checks untracked-but-not-ignored files (so a new file +# is caught before `git add`), so leaving these unignored reds the gate on every developer clone that has run a +# probe - a red that is the tree's, not the repository's (engine#1564). Ignoring them also stops run output being +# committed by accident. +.hrx123/logs/