Contributing to cov-loupe¶
Thank you for your interest in contributing! This project welcomes bug reports, improvements, and suggestions that make it more useful and reliable for the Ruby community.
How to Contribute¶
1. Reporting Issues¶
- Check existing issues before opening a new one.
- Include clear reproduction steps, expected vs. actual results, and your Ruby version (
ruby -v) and OS. - Keep discussion technical and respectful — see the Code of Conduct.
2. Submitting Changes¶
- Fork the repository on GitHub.
- Create a branch for your work:
- Install dependencies:
- Make your changes, conforming to the project's coding style.
- Run tests to verify your changes:
- Lint the code:
- Commit changes with clear, concise messages following conventional commit style (e.g.
fix: handle missing file gracefully). - Push your branch and open a Pull Request against
main.
PRs should: - Include or update tests for new/changed behavior.
- Pass all existing tests and RuboCop checks.
- Update documentation or README examples if behavior changes.
Development Setup¶
This project requires Ruby >= 3.2 (due to the mcp gem dependency). Typical workflow:
Optional tools: - rake as an alternate way to run rspec and rubocop - exe/cov-loupe the CLI and MCP entry point, use for end-to-end runs
Documentation¶
This project uses MkDocs with the Material theme to build and serve documentation.
Quick start:
For detailed platform-specific installation instructions (macOS, Linux, Windows) and troubleshooting, see the Documentation Development section of the Development Guide
Release Process (maintainer only)¶
- Update version in
lib/cov_loupe/version.rb - Update
RELEASE_NOTES.md - Commit, tag, and push:
- Build and publish:
Code of Conduct¶
Please review and follow the Code of Conduct. Instances of unacceptable behavior may be reported through GitHub’s Report Abuse form.
Thank you for helping improve cov-loupe!