Auto-force refresh and isolate experimental repo dir#509
Open
dustinvannoy-db wants to merge 1 commit intoexperimentalfrom
Open
Auto-force refresh and isolate experimental repo dir#509dustinvannoy-db wants to merge 1 commit intoexperimentalfrom
dustinvannoy-db wants to merge 1 commit intoexperimentalfrom
Conversation
Two related changes for experimental installs: 1. Use a separate clone dir for experimental (~/.ai-dev-kit/experimental-repo) so it doesn't clobber the stable ~/.ai-dev-kit/repo. Both install.sh and install.ps1 derive REPO_DIR/$RepoDir from the channel after arg parsing, and the prompt_mcp_path / Invoke-PromptMcpPath re-derivations also honor the channel. 2. Default FORCE=true on experimental installs (unless the user explicitly passed --force or set DEVKIT_FORCE). Previously, the skills-only path only cloned when the repo dir was missing, so reruns kept stale skills. Now when FORCE=true, that path also refreshes via fetch + reset --hard (falling back to delete + clone). Stable installs are unchanged. Co-authored-by: Isaac
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.
Summary
Two related changes so experimental installs always pick up the latest skills without clobbering the stable install:
Separate clone directory for experimental — experimental installs now clone into
~/.ai-dev-kit/experimental-repoinstead of~/.ai-dev-kit/repo. Stable and experimental installs no longer fight over the same checkout, so a user can have both side-by-side.Default
FORCE=trueon experimental installs — only when the user did not explicitly pass--forceor setDEVKIT_FORCE. Previously, the skills-only code path only cloned when the repo dir was missing, so reruns kept stale skill content. Now whenFORCE=true, that path also refreshes viagit fetch+reset --hard FETCH_HEAD, falling back to delete + re-clone if reset fails. Stable installs are unchanged.Behavior matrix
REPO_DIRFORCEinstall.sh(stable)~/.ai-dev-kit/repofalseinstall.sh --experimental~/.ai-dev-kit/experimental-repotrue(auto)install.sh --force~/.ai-dev-kit/repotrue(explicit)DEVKIT_FORCE=false install.sh --experimental~/.ai-dev-kit/experimental-repofalse(explicit env wins)install.ps1 --experimental(Windows)%USERPROFILE%\.ai-dev-kit\experimental-repotrue(auto)Test plan
install.sh --experimentalclones into~/.ai-dev-kit/experimental-repoinstall.sh --experimentalrefreshes the existingexperimental-repo(not silently using stale content)install.sh(stable) still uses~/.ai-dev-kit/repoand does not auto-forceDEVKIT_FORCE=false install.sh --experimentaldoes NOT refresh the cached repo (explicit env wins)install.ps1 --experimentalclones into%USERPROFILE%\.ai-dev-kit\experimental-repoinstall.ps1 --experimentalrefreshes the existing experimental-repoThis pull request and its description were written by Isaac.