Skip to content

Fix Gemini CLI installer preflight on fresh clones#166

Open
stablegenius49 wants to merge 1 commit intomsitarzewski:mainfrom
stablegenius49:pr-factory/issue-165-gemini-install-preflight
Open

Fix Gemini CLI installer preflight on fresh clones#166
stablegenius49 wants to merge 1 commit intomsitarzewski:mainfrom
stablegenius49:pr-factory/issue-165-gemini-install-preflight

Conversation

@stablegenius49
Copy link

What does this PR do?

Fixes the Gemini CLI installer so a fresh clone fails with a clear preflight message instead of a raw cp: ... No such file or directory error when the generated extension artifacts are missing.

Changes

  • check for integrations/gemini-cli/gemini-extension.json before copying it
  • check for integrations/gemini-cli/skills/ before copying generated skills
  • point both failures to ./scripts/convert.sh --tool gemini-cli
  • update README.md, integrations/README.md, and integrations/gemini-cli/README.md to document the required convert step on fresh clones

Verification

  • reproduced the current failure on a clean upstream clone (cp: ... gemini-extension.json: No such file or directory)
  • ran bash -n scripts/install.sh
  • verified the patched installer now fails with a clear message when generated Gemini files are missing
  • ran ./scripts/convert.sh --tool gemini-cli
  • verified ./scripts/install.sh --tool gemini-cli succeeds against a temporary HOME and installs the manifest + 142 generated skills

Closes #165.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

install.sh --tool gemini-cli fails on a fresh clone because required generated integration files are missing

2 participants