Contributing
How to contribute to RepliMap
Thank you for your interest in contributing to RepliMap!
Getting Started
-
Fork the repository
-
Clone your fork:
git clone https://github.com/YOUR_USERNAME/replimap.git cd replimap -
Install development dependencies:
pip install -e ".[dev]" -
Create a feature branch:
git checkout -b feature/your-feature-name
Development Workflow
Running Tests
# Run all tests
pytest
# Run with coverage
pytest --cov=replimap
# Run specific test file
pytest tests/test_scanner.pyCode Style
We use ruff for linting and formatting:
# Check for issues
ruff check .
# Auto-fix issues
ruff check --fix .
# Format code
ruff format .Type Checking
mypy replimapPull Request Guidelines
- Create a feature branch from
main - Make your changes with clear commit messages
- Add tests for new functionality
- Ensure all tests pass
- Update documentation if needed
- Submit a pull request with a clear description
Commit Message Format
type: short description
Longer description if needed.
Fixes #123Types: feat, fix, docs, refactor, test, chore
Reporting Issues
Bug Reports
Open an issue on GitHub with:
- Description of the bug
- Steps to reproduce
- Expected vs actual behavior
- RepliMap version (
replimap --version) - Python version
- OS
Security Issues
Do not open public issues for security vulnerabilities.
Email support@replimap.com instead.
Questions?
- General: hello@replimap.com
- Technical Support: support@replimap.com
- Discussions: GitHub Discussions