Fix repo-assist memory validation rejecting .git directory - #1454
Merged
BenjaminMichaelis merged 1 commit intoOct 3, 2026
Merged
Conversation
The repo-memory root is a git clone, so the exact-one-entry check always failed on .git. Ignore .git, drop the legacy-file rmSync (gh-aw rejects validators that modify memory), and restore max-file-count to 1 now that legacy files are gone. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
BenjaminMichaelis
deleted the
benjaminmichaelis-fix-repo-memory-validation
branch
October 3, 2026 07:18
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.
Fixes the
Custom repo-memory validation failed for 'default'error in run 37099697573.Cause
gh-aw sets
memoryRootto agit cloneofmemory/repo-assist, so the folder always contains.gitnext tonotes.json. The validator required exactly one entry, so it failed even though the memory was valid.Changes (
.github/workflows/repo-assist.md+ recompiled lock).gitbefore running the "onlynotes.json" check.fs.rmSynclegacy-file cleanup. gh-aw fails validators that change memory files, and the legacy files are already gone from the branch.max-file-countback to1, since the one-time legacy cleanup is finished.Validation
gh aw compile repo-assist --strictsucceeds.memory/repo-assist. It passes, and still fails when an extraextra.jsonis added.Security review note
gh aw compileflagged one item needing approval: Memory validation script changes: repo-memory:default (modified). That is the edit described above. It adds or removes no secrets, actions, or network access.Not addressed
The same run also failed in the Copilot CLI step with
400 Invalid 'input[N].id': 'ctc_call_…'. Expected an ID that begins with 'fc'. That error comes from Copilot CLI or the gh-aw harness, not this repo, and should be reported upstream.