gitignore: blanket-ignore benchmarks/perturbation/configs/#92
Merged
Conversation
Replaces the per-pattern config ignore list with a single `configs/` rule, and untracks the 5 example configs that were previously checked in. Configs/ is effectively a local experiment log — every per-domain × per-system YAML accumulates here as we iterate, and they don't survive code review or carry useful history. Files removed from tracking but kept on disk: - default.yaml, coarse_medium.yaml, coarse_short.yaml - surface_errors.yaml, surface_errors_medium.yaml Follow-up after PR #85 lands: untrack the 8 full_*_reviewer3.yaml configs it adds, since they're effectively local convention rather than something the test/CI matrix references.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Treats
benchmarks/perturbation/configs/as a local experiment log rather than tracked code.configs/_*,configs/full_*.yaml,configs/grok_*.yaml,configs/longtail_*.yaml,configs/subset_*.yaml,configs/r3_smoke*.yaml+ exception) with a single blanketconfigs/ruledefault.yaml,coarse_medium.yaml,coarse_short.yaml,surface_errors.yaml,surface_errors_medium.yamlIn practice every per-domain × per-system YAML in here is a one-off run (we accumulate dozens during exploration) — they don't survive code review or carry useful history. Anyone reproducing a run starts from
default.yamlexamples in the README, not from whatever happens to be checked in.Follow-up
Once PR #85 lands, untrack the 8
full_*_reviewer3.yamlconfigs it adds for the same reason.Test plan
git check-ignore -v benchmarks/perturbation/configs/anything.yamlmatches the newconfigs/rule🤖 Generated with Claude Code