fix(security): gitignore MCP configs with API tokens#17
Merged
Conversation
Prevent MCP configuration files containing API tokens from being tracked. These files are generated by `dvmi sync-config-ai` and must remain local-only. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Coverage Report |
QA Report
|
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
.mcp.jsonandopencode.jsonto.gitignoreto prevent MCP config files containing API tokens from being committeddvmi sync-config-aifor project-scoped AI environments and must remain local-onlygit filter-repoto purge previously committed JWT tokens from all branches and tagsTest plan
git log --all -- .mcp.json opencode.jsonreturns empty (files purged from history)git statusis clean (files exist on disk but are ignored)🤖 Generated with Claude Code