fix(git_clone): Fix git_clone cwd so clone runs from parent of destin… #33
Conversation
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
ABHIRAMSHIBU
commented
Nov 24, 2025
ABHIRAMSHIBU
commented
- resolve the clone target to an absolute path and run git from its parent
- avoid spawning git with a non-existent cwd that reported “Git command not found”
…ation - resolve the clone target to an absolute path and run git from its parent - avoid spawning git with a non-existent cwd that reported “Git command not found” Co-authored-by: Preet Patel <preet.makz@gmail.com>
yasien-c
added a commit
to yasien-c/git-mcp-server
that referenced
this pull request
Dec 2, 2025
- Add Dockerfile with multi-stage Bun build on Debian - Optimize .dockerignore for smaller build context - Fix path resolution bug that caused ENOENT errors (PR cyanheads#33)
yasien-c
added a commit
to yasien-c/git-mcp-server
that referenced
this pull request
Dec 2, 2025
Resolves issue where clone failed with 'posix_spawn git' error because the target directory doesn't exist yet. Now clones from parent dir. Ref: cyanheads#33
yasien-c
added a commit
to yasien-c/git-mcp-server
that referenced
this pull request
Dec 2, 2025
* feat: add Docker support with path validation fix - Add Dockerfile with multi-stage Bun build on Debian - Optimize .dockerignore for smaller build context - Fix path resolution bug that caused ENOENT errors (PR cyanheads#33) * ci: add GHCR Docker image build workflow - Build and push to ghcr.io on main branch push - Multi-platform support (amd64, arm64) - Semantic versioning tags on release - Manual trigger with custom tag support * fix(clone): run git clone from parent directory to avoid ENOENT Resolves issue where clone failed with 'posix_spawn git' error because the target directory doesn't exist yet. Now clones from parent dir. Ref: cyanheads#33 * feat(clone): enhance URL validation for repository cloning Updated the input schema to enforce a minimum length for the repository URL and clarified the supported URL formats (HTTPS and SSH) in the description. This improves user guidance and input validation for the git clone tool.
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.