Skip to content

Conversation

@olaservo
Copy link
Member

This server is out of order and keeps popping up as a conflict.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

@olaservo olaservo requested a review from tadasant May 11, 2025 21:01
@olaservo olaservo enabled auto-merge May 11, 2025 21:13
@olaservo olaservo mentioned this pull request May 11, 2025
12 tasks
tadasant
tadasant previously approved these changes May 12, 2025
@tadasant
Copy link
Member

@olaservo active conflict :\

@tadasant
Copy link
Member

I fixed -- I think you can approve and merge now even though I can't

@olaservo olaservo closed this Jun 5, 2025
auto-merge was automatically disabled June 5, 2025 03:16

Pull request was closed

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.

3 participants