Skip to content

chore: untrack artifacts/ + gitignore Anvil smoke output#17

Merged
LightDriverCS merged 1 commit into
mainfrom
chore/gitignore-anvil-artifacts
Apr 28, 2026
Merged

chore: untrack artifacts/ + gitignore Anvil smoke output#17
LightDriverCS merged 1 commit into
mainfrom
chore/gitignore-anvil-artifacts

Conversation

@LightDriverCS

Copy link
Copy Markdown

Summary

Cleanup follow-up from #16. The Anvil repair commit's `git add -A` accidentally committed 98 local Anvil smoke artifact files (~7.4 MB) under `artifacts/anvil/` because `.gitignore` had `.artifacts/` (dot prefix) but not `artifacts/`.

Why

The smoke script (`scripts/anvil_pr_smoke.sh`) writes to `${repo_root}/artifacts/anvil/` — codex-anvil-prompt.md, codex-anvil-report.md, codex-anvil.log, anvil-repair.patch, etc. Per-PR per-timestamp. Local debug output that doesn't belong in the repo.

Changes

  • `.gitignore`: add `artifacts/anvil/`
  • `git rm -r --cached artifacts/` (untracks 98 files; data stays in git history since no force-push)

Test plan

  • `git status` after commit shows clean tree
  • Future smokes write to `artifacts/anvil/` without staging
  • Repo size on main reflects untracked state (data stays in history but no future bloat)

🤖 Generated with Claude Code

PR #16 accidentally committed ~7.4 MB / 98 files of local Codex
Anvil smoke artifacts (codex-anvil-{prompt,report,log}.md,
anvil-repair.patch, etc.) under artifacts/anvil/. The smoke script
writes to repo_root/artifacts/anvil/ but only `.artifacts/` (with
dot prefix) was gitignored, not `artifacts/` (no prefix).

Adds `artifacts/anvil/` to .gitignore and untracks the existing
files. The data stays in git history (no force-push); future
smokes won't add new files to the index.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
@LightDriverCS
LightDriverCS merged commit 86fdeb2 into main Apr 28, 2026
3 of 10 checks passed
@LightDriverCS
LightDriverCS deleted the chore/gitignore-anvil-artifacts branch April 28, 2026 15:14
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.

1 participant