- Streamline README, API, architecture, and usage documentation - Reduce complexity and focus on core functionality - Update roadmap with more pragmatic, near-term goals - Simplify contributing guidelines - Improve overall documentation clarity and readability
1.9 KiB
1.9 KiB
layout, title, nav_order
| layout | title | nav_order |
|---|---|---|
| default | Contributing | 5 |
Contributing Guide 🤝
Thank you for your interest in contributing to the MCP Server project!
Getting Started
Prerequisites
- Bun >= 1.0.26
- Home Assistant instance
- Basic understanding of TypeScript
Development Setup
-
Fork the repository
-
Clone your fork:
git clone https://github.com/YOUR_USERNAME/homeassistant-mcp.git cd homeassistant-mcp -
Install dependencies:
bun install -
Configure environment:
cp .env.example .env # Edit .env with your Home Assistant details
Development Workflow
Branch Naming
feature/- New featuresfix/- Bug fixesdocs/- Documentation updates
Example:
git checkout -b feature/device-control-improvements
Commit Messages
Follow simple, clear commit messages:
type: brief description
[optional detailed explanation]
Types:
feat:- New featurefix:- Bug fixdocs:- Documentationchore:- Maintenance
Code Style
- Use TypeScript
- Follow existing code structure
- Keep changes focused and minimal
Testing
Run tests before submitting:
# Run all tests
bun test
# Run specific test
bun test test/api/control.test.ts
Pull Request Process
- Ensure tests pass
- Update documentation if needed
- Provide clear description of changes
PR Template
## Description
Brief explanation of the changes
## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Documentation update
## Testing
Describe how you tested these changes
Reporting Issues
- Use GitHub Issues
- Provide clear, reproducible steps
- Include environment details
Code of Conduct
- Be respectful
- Focus on constructive feedback
- Help maintain a positive environment
Resources
Thank you for contributing!