Merged
Conversation
Force git fetches when refreshing cached skill repositories so\nretagged refs do not fail with would clobber existing tag errors.\nThis keeps dotagents aligned with the remote state for mutable refs\nlike major version tags while leaving SHA-pinned installs unchanged.\n\nAdd regression coverage for the fetch commands and the age-gate\nunshallow path so the cache update behavior stays explicit.\n\nCo-Authored-By: OpenAI Codex <noreply@openai.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Force cached git fetches when refreshing skill repositories.
Dotagents reuses cached clones under
~/.local/dotagents, and a plaingit fetchcan fail when an upstream named ref likev0has been retagged since the cache was created. In that case install fails withwould clobber existing tageven though the cache should just track the current remote state.This updates the cache refresh paths to use
git fetch --forcefor default branch refreshes, ref fetches, and the age-gate unshallow path. That keeps the cache aligned with the remote for mutable refs while leaving SHA-pinned installs unchanged.The tests now assert the forced fetch arguments so this behavior stays covered.
pnpm checkpasses locally.wardencould not run in this environment because the configured command points at a missing local build:/Users/greg/code/warden/dist/cli/index.js.