chore: gitignore pipeline runtime state (.pipeline/.runtime, .pipeline/.stats) - #51
Merged
Merged
Conversation
…e/.stats) The ai-pipeline plugin writes machine-generated runtime state into `<repo>/.pipeline/.runtime/` (events.jsonl, transcript .offset files) in whatever repo it runs in. Untracked, that state shows up as repo dirt and blocks the main-checkout cleanliness gate in our orchestration tooling. Mirrors the pattern already in the `software` superproject root .gitignore: ignore the `.runtime/` and `.stats/` siblings only, NOT the whole `.pipeline/` directory — `.pipeline/.hooks/` is deliberately tracked (the plugin resolves consumer worktree hooks from `<root>/.pipeline/.hooks`) and must stay trackable here if this repo later gains real pipeline hooks. Verified with `git check-ignore -v`: `.pipeline/.runtime/events.jsonl` and `.pipeline/.stats/foo.json` both match the new lines, while `.pipeline/.hooks/worktree-create.py` is NOT ignored. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AGfFF7821pBRND3VrdMVaw
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.
Problem
The
ai-pipelineplugin writes machine-generated runtime state into<repo>/.pipeline/.runtime/(anevents.jsonlplus transcript.offsetfiles)in whatever repo it runs in. Because that state is untracked and unignored, it
shows up as repo dirt — which in turn blocks the
--parallel>1main-checkoutcleanliness gate in our orchestration tooling.
Fix
Ignore the two machine-generated siblings, mirroring the pattern already in the
softwaresuperproject root.gitignore:Note this deliberately ignores the siblings only, not the whole
.pipeline/directory:.pipeline/.hooks/is tracked on purpose (the pipelineplugin resolves the consumer's worktree hooks from
<root>/.pipeline/.hooks),so it must stay trackable here if this repo ever gains real pipeline hooks.
Verification
git check-ignore -vagainst the new lines:.pipeline/.runtime/events.jsonl.pipeline/.runtime/.pipeline/.stats/foo.json.pipeline/.stats/.pipeline/.hooks/worktree-create.pyAlso confirmed against real files on disk: with all four paths materialised,
git status --porcelain -ualllists only.pipeline/.hooks/worktree-create.pyas untracked; the runtime and stats files are invisible. Probe files removed
before committing.
No other content in
.gitignorewas reordered or reformatted.