|
| 1 | +# Contributing to SQLAlchemy-ViewORM |
| 2 | + |
| 3 | +Thank you for your interest in contributing to SQLAlchemy-ViewORM! This document provides guidelines and instructions for contributing to this project. |
| 4 | + |
| 5 | +## Code of Conduct |
| 6 | + |
| 7 | +By participating in this project, you agree to abide by our code of conduct: be respectful, considerate, and collaborative. |
| 8 | + |
| 9 | +## How to Contribute |
| 10 | + |
| 11 | +### Reporting Bugs |
| 12 | + |
| 13 | +If you find a bug, please submit an issue with: |
| 14 | + |
| 15 | +1. A clear and descriptive title |
| 16 | +2. Steps to reproduce the bug |
| 17 | +3. Expected behavior |
| 18 | +4. Actual behavior |
| 19 | +5. Environment details (OS, Python version, SQLAlchemy version, etc.) |
| 20 | +6. Any additional context that might help |
| 21 | + |
| 22 | +### Suggesting Enhancements |
| 23 | + |
| 24 | +We welcome suggestions for enhancements! Please submit an issue with: |
| 25 | + |
| 26 | +1. A clear and descriptive title |
| 27 | +2. A detailed description of the proposed enhancement |
| 28 | +3. Examples of how the enhancement would be used |
| 29 | +4. Any relevant context or background |
| 30 | + |
| 31 | +### Pull Requests |
| 32 | + |
| 33 | +We actively welcome pull requests. Here's how to submit one: |
| 34 | + |
| 35 | +1. Fork the repository |
| 36 | +2. Create a new branch (`git checkout -b feature/amazing-feature`) |
| 37 | +3. Make your changes |
| 38 | +4. Run tests to ensure they pass |
| 39 | +5. Commit your changes (`git commit -m 'Add some amazing feature'`) |
| 40 | +6. Push to the branch (`git push origin feature/amazing-feature`) |
| 41 | +7. Open a Pull Request |
| 42 | + |
| 43 | +## Development Setup |
| 44 | + |
| 45 | +1. Clone your fork of the repository |
| 46 | +2. Install development dependencies: |
| 47 | + ```bash |
| 48 | + pip install -e ".[dev]" |
| 49 | + ``` |
| 50 | +3. Install pre-commit hooks: |
| 51 | + ```bash |
| 52 | + pre-commit install |
| 53 | + ``` |
| 54 | + |
| 55 | +## Testing |
| 56 | + |
| 57 | +We use pytest for testing. Run the tests with: |
| 58 | + |
| 59 | +```bash |
| 60 | +pytest |
| 61 | +``` |
| 62 | + |
| 63 | +For coverage reports: |
| 64 | + |
| 65 | +```bash |
| 66 | +pytest --cov=sqlalchemy_view_orm |
| 67 | +``` |
| 68 | + |
| 69 | +## Code Style |
| 70 | + |
| 71 | +We follow these coding standards: |
| 72 | + |
| 73 | +- Black for code formatting |
| 74 | +- isort for import sorting |
| 75 | +- mypy for type checking |
| 76 | +- flake8 for linting |
| 77 | + |
| 78 | +You can run these tools manually or use pre-commit hooks. |
| 79 | + |
| 80 | +## Documentation |
| 81 | + |
| 82 | +When adding new features, please update the relevant documentation: |
| 83 | + |
| 84 | +- Update docstrings for public classes and methods |
| 85 | +- Update README.md if necessary |
| 86 | +- Add examples if appropriate |
| 87 | + |
| 88 | +## Versioning |
| 89 | + |
| 90 | +We use [Semantic Versioning](https://semver.org/) (MAJOR.MINOR.PATCH). |
| 91 | + |
| 92 | +## Release Process |
| 93 | + |
| 94 | +1. Update version in `sqlalchemy_view_orm/__init__.py` |
| 95 | +2. Update CHANGELOG.md |
| 96 | +3. Create a new GitHub release with the version number |
| 97 | + |
| 98 | +## Getting Help |
| 99 | + |
| 100 | +If you need help with the contribution process, feel free to open an issue with your question. |
| 101 | + |
| 102 | +## License |
| 103 | + |
| 104 | +By contributing to SQLAlchemy-ViewORM, you agree that your contributions will be licensed under the project's MIT License. |
0 commit comments