Skip to content

[Template Sync] fix: update sync workflow to use .mcp.json for cursor repo - #27

Closed
liukatkat wants to merge 1 commit into
mainfrom
template-sync/23c3c994f3a1e3d4135c78e962a05a1c8ba8bb50
Closed

[Template Sync] fix: update sync workflow to use .mcp.json for cursor repo#27
liukatkat wants to merge 1 commit into
mainfrom
template-sync/23c3c994f3a1e3d4135c78e962a05a1c8ba8bb50

Conversation

@liukatkat

Copy link
Copy Markdown
Collaborator

Template Sync

This PR was automatically generated from a merge to the template repository.

Source commit: 23c3c994f3a1e3d4135c78e962a05a1c8ba8bb50


Version Bump

Please add one of the following labels before merging:

  • bump:patch - Bug fixes (0.4.1 → 0.4.2)
  • bump:minor - New features (0.4.1 → 0.5.0)
  • bump:major - Breaking changes (0.4.1 → 1.0.0)

Generated by mcp-marketplace-template

Check if Semgrep is installed, and install it if not:

```bash
which semgrep || brew install semgrep

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Semgrep identified an issue in your code:
Instead of documenting the brew commands you want people to run, you can just commit a Brewfile to the repo and ask that they run brew bundle.

To resolve this comment:

✨ Commit Assistant Fix Suggestion
  1. Create a Brewfile in your repository (if it doesn't already exist).
  2. Add brew "semgrep" to your Brewfile.
  3. Replace which semgrep || brew install semgrep in your documentation or setup instructions with brew bundle or brew bundle --file=Brewfile if your Brewfile isn't in the root directory.

Alternatively, if you want to provide a platform-independent install, consider suggesting python3 -m pip install semgrep instead. Using a Brewfile makes it easier to manage and update dependencies for everyone using the repository.

💬 Ignore this finding

Reply with Semgrep commands to ignore this finding.

  • /fp <comment> for false positive
  • /ar <comment> for acceptable risk
  • /other <comment> for all other reasons

Alternatively, triage in Semgrep AppSec Platform to ignore the finding created by use-brewfile.

You can view more details about this finding in the Semgrep AppSec Platform.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant