Skip to content

chore: untrack the per-run langsmith worker-attempt artifact #2856

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stranske merged 1 commit into from
Jul 31, 2026
Merged

chore: untrack the per-run langsmith worker-attempt artifact #2856

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,7 +142,11 @@ test_parser_debug.js
# agents_verifier_context.js) and stray one-off fix patches.
# coverage-local.* / pytest-junit*.xml are per-run CI snapshots regenerated by
# reusable-10-ci-python.yml; artifacts/ holds ad-hoc committed run outputs.
# langsmith-fleet-worker-attempt.json is written per-run by reusable-codex-run.yml
# and uploaded as an artifact; while tracked, every run that rewrote it produced a
# diff that codex-autofix then committed onto whatever PR happened to be open.
*.patch
coverage-local.*
pytest-junit*.xml
langsmith-fleet-worker-attempt.json

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 31, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Propagate the artifact exclusion to consumer repositories

When reusable-codex-run.yml executes for a consumer, agent-run-base checks out that consumer at the workspace root, the artifact step writes this file there, and the later commit step runs git add -A. This ignore rule exists only in the Workflows root; templates/consumer-repo/.gitignore and the canonical patterns used by sync_status_file_ignores.py still omit it, so consumer runs will continue committing the per-run artifact. Add it to the consumer status-file block and fallback patterns for propagation, or explicitly unstage it in the reusable runner.

AGENTS.md reference: AGENTS.md:L39-L41

Useful? React with 👍 / 👎.

artifacts/
4 changes: 4 additions & 0 deletions config/root-allowlist.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,10 @@
.coderabbit.yaml
.flake8
.gitattributes
.gitignore
.langsmith-smoke-test.txt
.pre-commit-config.yaml
.release-please-manifest.json
AGENTS.md
CHANGELOG.md
CLAUDE.md
Expand All @@ -24,6 +26,8 @@ find_duplicate_tokens.sh
input.txt
manage_sync_prs.sh
pyproject.toml
release-please-config.json
renovate.json
requirements.lock
requirements.txt
sitecustomize.py
Expand Down
16 changes: 0 additions & 16 deletions langsmith-fleet-worker-attempt.json
View file
Open in desktop

This file was deleted.

Loading