Repository navigation
chore(repo): stop tracking the agent instruction files git ignored anyway - #30
Merged
Merged
Conversation
…yway `.gitignore` has listed AGENTS.md and CLAUDE.md for a while, and the entries did nothing: both files were already tracked, and an ignore rule only ever applies to a file git is not following yet. So every session opened on a working tree with two files reported as modified — amenbo and wharfy rewrite their managed blocks in place, and the pending diff here is exactly that (`AMENBO_ACTOR=ai` becoming `--actor ai` in the v2 block). Untrack them and let the existing rule take effect. Both files stay on disk, so the tools that read them keep working; the copies already in history stay there too, which is fine — nothing in them is private. One thing does leave the repo with them: the hand-written note on distribution being a separate, deliberate step, which sat outside the managed blocks. It is not the only place that rule is written — release.yml and promote.yml encode it, and the comment in promote.yml says so — but a fresh clone no longer reads it in prose. amenbo-task: #2722 Co-Authored-By: Claude Opus 5 (1M context) <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.
.gitignorehas listedAGENTS.mdandCLAUDE.mdfor a while, and the entries did nothing: both files were already tracked, and an ignore rule only applies to a file git is not following yet. Every session therefore opened on a working tree with two files reported as modified — amenbo and wharfy rewrite their managed blocks in place, and the pending diff was exactly that.Untrack them so the existing rule takes effect. Both files stay on disk, so the tools that read them keep working. The copies already in history stay there too; nothing in them is private.
One thing leaves the repo with them: the hand-written note on distribution being a separate, deliberate step, which sat outside the managed blocks.
release.ymlandpromote.ymlstill encode that rule, but a fresh clone no longer reads it in prose.amenbo-task: #2722