fix: resolve macOS setup compatibility and add documentation commit step (fixes #11, #16)#33
Closed
Ashwinhegde19 wants to merge 2 commits intogemini-cli-extensions:mainfrom
Closed
Conversation
- Update gemini-extension.json version from 0.1.0 to 0.1.1 to match latest release - Add troubleshooting section to README addressing 401 errors during installation - Document workarounds for GitHub API rate limiting issues (issue gemini-cli-extensions#20) Fixes gemini-cli-extensions#20
- Fix setup.toml: Replace ls -lR -I with cross-platform find command - macOS/BSD ls doesn't support -I flag, causing node_modules to be scanned - Use find command with prune option which works on all platforms - Add __pycache__ to exclusion list - Fix implement.toml: Add automatic commit step after documentation synchronization - Previously, documentation updates (product.md, tech-stack.md, product-guidelines.md) were not committed - Add section 7: Commit Documentation Updates - Rename section 7 to 8 (TRACK CLEANUP) - Update execution trigger to include commit requirement Fixes gemini-cli-extensions#11 (setup token limit on macOS) and gemini-cli-extensions#16 (uncommitted files after implementation)
nexus-infinity
approved these changes
Dec 31, 2025
nexus-infinity
approved these changes
Dec 31, 2025
Collaborator
|
Hey @Ashwinhegde19 , thanks for the PR! Good catch on the macOS/BSD incompatibility. On the the missing documentation commit, we actually already fixed that in PR #48. Feel free to pull the latest changes and update this PR to include only the macOS/BSD compatibility fix, or submit a fresh PR if that's easier. |
Collaborator
|
Fresh PR with the requested changes was started in #56. Closing this PR. |
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.
Summary
This PR addresses two critical bugs affecting user experience:
/conductor:setupdue to token limit errorsChanges
1. Fix macOS/BSD compatibility in setup.toml (Issue #11)
ls -lR -I 'node_modules'command fails silently on macOS/BSD systems because the-Iflag is not supported. This causesnode_modulesand other directories to be scanned, leading to API token limit errors.findcommand that works on all systems:__pycache__to exclusion list/conductor:setupwithout hitting token limits2. Add automatic documentation commit step in implement.toml (Issue #16)
product.md,tech-stack.md, andproduct-guidelines.md, but these changes are not committed automatically. Users must manually commit these files.conductor(doc-sync): Update documentation for '<track_description>'Testing
Both fixes have been tested and work as expected:
Fixes