Skip to content

Fix GitHub CI lint and formatting errors#20

Merged
yokuze merged 1 commit into
mainfrom
fix/ci-errors-2257419898391673200
Apr 10, 2026
Merged

Fix GitHub CI lint and formatting errors#20
yokuze merged 1 commit into
mainfrom
fix/ci-errors-2257419898391673200

Conversation

@yokuze

@yokuze yokuze commented Apr 9, 2026

Copy link
Copy Markdown
Member

I have fixed several linting and formatting issues that were likely causing the GitHub CI failures on the main branch.

Key changes:

  1. TypeScript Linting: Removed unused PLUGIN_VERSION_CARGO imports and fixed whitespace issues in packages/mcp-server/src/prompts-registry.ts and packages/mcp-server/src/tools-registry.ts.
  2. Rust Formatting: Ran cargo fmt in packages/tauri-plugin-mcp-bridge to fix formatting inconsistencies.
  3. Verification: Verified that npm run eslint and cargo fmt -- --check now pass successfully. Unit tests for both the MCP server and the Rust plugin also pass.
  4. Cleanup: Removed a large log file (packages/test-app/tauri_dev.log) that was accidentally created during the investigation.

PR created automatically by Jules for task 2257419898391673200 started by @yokuze

- Remove unused PLUGIN_VERSION_CARGO imports in prompts and tools registry
- Fix multiple blank lines and comment spacing in TypeScript files
- Apply cargo fmt to tauri-plugin-mcp-bridge
- Remove accidental tauri_dev.log artifact
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@yokuze yokuze merged commit 687f662 into main Apr 10, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant