modelcontextprotocol / modelcontextprotocol/servers
.git folder staged by running 'git add .'
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
Describe the bug
Claude called git add ., which resulted in the .git folder itself being added to git
To Reproduce
Steps to reproduce the behavior:
- Get Claude to call
git add .(this can happen in multiple ways, so not 'exact steps')
Expected behavior
A clear and concise description of what you expected to happen.
Logs
If applicable, add logs to help explain your problem.
`git status
On branch main
Your branch is ahead of 'origin/main' by 2 commits.
(use "git push" to publish your local commits)
Changes not staged for commit:
(use "git add/rm ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified: ./.git/config
modified: ./.git/index
modified: ./.git/logs/HEAD
`
Additional context
Add any other context about the problem here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is identified in the issue. Start by reproducing the reported git add . behavior and inspect the repository's handling of git commands; clarify the intended behavior with the issue discussion. Done should be demonstrated by a regression test or reproduction showing that the .git directory is not staged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100