Thank you for your interest in contributing! This document provides guidelines and steps for contributing to this project.
By participating in this project, you agree to abide by our Code of Conduct.
- Check existing issues to avoid duplicates
- Open a new issue using the Bug Report template
- Include steps to reproduce, expected vs. actual behavior, and environment details
- Open an issue using the Feature Request template
- Describe the use case and why the feature would be valuable
- Fork the repository
- Create a feature branch:
git checkout -b feature/your-feature - Make your changes following the coding standards below
- Write or update tests as needed
- Commit using Conventional Commits:
feat:new featurefix:bug fixdocs:documentationchore:maintenancerefactor:code restructuringtest:test changes
- Push and open a Pull Request against
main
Use prefixed branch names:
feature/— new functionalityfix/— bug fixeschore/— maintenancedocs/— documentation
- Follow existing code patterns and conventions
- No broad exception handling (catch specific exceptions)
- Add appropriate error handling
- Ensure tests pass before submitting
- Fill out the PR template completely
- Link related issues
- Ensure CI passes
- Request review from a maintainer
- Address review feedback promptly
See README.md for setup instructions.
Open a discussion or reach out at musictechlab.io/contact.