Contributing to MCPCTL
Thank you for your interest in contributing to MCPCTL! This document provides guidelines and instructions for contributing to the project.
๐ฏ Getting Started
- Fork the repository
- Clone your fork:
git clone https://github.com/your-username/mcpctl.git
- Create a new branch:
git checkout -b feature/your-feature-name
๐ ๏ธ Development Setup
- Install pnpm if you haven't already:
npm install -g pnpm
Or use corepack to enable pnpm:
corepack enable pnpm
- Install dependencies:
pnpm install
- Run tests:
pnpm test
- Build the project:
pnpm build
๐ Code Style
- We use ESLint and Prettier for code formatting
- Follow the existing code style and conventions
- Write meaningful commit messages
- Add comments for complex logic
๐งช Testing
- Write tests for new features
- Ensure all tests pass before submitting PR
- Add test cases for edge cases
- Update existing tests if modifying functionality
๐ Documentation
- Update documentation for new features
- Add examples for new commands
- Keep the README.md up to date
- Document any breaking changes
๐ Pull Request Process
- Update the README.md with details of changes if needed
- Update the documentation if you're changing functionality
- The PR will be merged once you have the sign-off of at least one maintainer
- Make sure the CI checks pass
๐ Bug Reports
When filing a bug report, please include:
- A clear, descriptive title
- Steps to reproduce the issue
- Expected behavior
- Actual behavior
- Screenshots if applicable
- Environment details (OS, Node.js version, etc.)
โจ Feature Requests
We welcome feature requests! When suggesting a new feature:
- Explain why this feature would be useful
- Describe how you envision it working
- Provide examples of similar features in other tools
- Consider contributing the feature yourself
๐ License
By contributing to MCPCTL, you agree that your contributions will be licensed under the project's MIT License.