Skip to content

chore(gitignore): match the run_notes directory csv mode writes - #208

Closed
lfnothias wants to merge 1 commit into
mimosa_v2from
propose/gitignore-run-notes
Closed

chore(gitignore): match the run_notes directory csv mode writes#208
lfnothias wants to merge 1 commit into
mimosa_v2from
propose/gitignore-run-notes

Conversation

@lfnothias

Copy link
Copy Markdown
Collaborator

Problem

.gitignore lists runs_notes/* twice, but csv_mode.py writes benchmark manifests under run_notes/, so every benchmark run leaves run_notes/benchmark_manifest.json untracked in the working tree.

Solution

Replace both entries with one run_notes/*.

Testing

With a run_notes/benchmark_manifest.json present, git status --short is empty on this branch.

Backwards compatibility

Not affected.

🤖 Generated with Claude Code

.gitignore listed runs_notes/* twice, but csv_mode.py writes benchmark
manifests under run_notes/, so a run left an untracked file in the tree.
Use the real name once.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@Fosowl

Fosowl commented Sep 3, 2026

Copy link
Copy Markdown
Member

Closing. First, a question this raises rather than answers: where does benchmark_manifest.json come from in the first place? This change should have been linked to whatever PR introduced that file. As far as I can tell it comes from #198's evaluation changes, which are themselves an anti-pattern (a separated evaluation system (different repo) should consume capsules produced by the normal pipeline, not add new artifacts to it). Separately: no files under run_notes should ever be committed.

@Fosowl Fosowl closed this Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants