Repository navigation
Say where the parity artifacts belong - #51
Open
anakanemison wants to merge 1 commit into
Open
anakanemison wants to merge 1 commit into
anakanemison wants to merge 1 commit into
Conversation
The procedure listed the parity artifacts to produce (the two models, aquery.json, diff.json) but said only that they live "in or beside" the target repo, so where they ended up was up to the agent. Measured in any2bazel-lab: one migration wrote its diff and both models to a session-scoped temp directory, so nothing in the repository showed that it had converged; another kept them at the repo root, gitignored them, and recorded how to regenerate them, unprompted. The preamble now says: at the target repo root beside any2bazel.json, gitignored with a comment naming the regeneration command, not in a temp directory. That makes a migration auditable by default without committing large generated JSON. In the lab's later graphicsgems and lensfun runs with this change, the artifacts were at the root, gitignored, with the regeneration command. Lab-Proposal: P6 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Part 16 of 23 of a stacked series (tracking issue: #35). Based on
U15-version-stamp, the previous part: review and merge that first.Kind: guidance. Lab proposal: P6.
What the migration runs showed
Parity artifacts landed in arbitrary places; with this, at the repository root, gitignored, with the command that regenerates them.
The change
The procedure listed the parity artifacts to produce (the two models,
aquery.json, diff.json) but said only that they live "in or beside" the
target repo, so where they ended up was up to the agent.
Measured in any2bazel-lab: one migration wrote its diff and
both models to a session-scoped temp directory, so nothing in the
repository showed that it had converged; another kept them at the repo
root, gitignored them, and recorded how to regenerate them, unprompted.
The preamble now says: at the target repo root beside any2bazel.json,
gitignored with a comment naming the regeneration command, not in a temp
directory. That makes a migration auditable by default without committing
large generated JSON.
In the lab's later graphicsgems and lensfun runs with this change, the
artifacts were at the root, gitignored, with the regeneration command.
Testing
pytest tests/at this commit: 196 passed (130 onmain).🤖 Generated with Claude Code