|
| 1 | +# Contributing |
| 2 | + |
| 3 | +This document outlines how to contribute to the gotenberg-client project effectively. |
| 4 | + |
| 5 | +## Questions and Support |
| 6 | + |
| 7 | +For general questions and support, please use our [Q&A Discussions](https://github.com/stumpylog/gotenberg-client/discussions/categories/q-a) forum. |
| 8 | + |
| 9 | +## Feature Requests |
| 10 | + |
| 11 | +We use the [Ideas category in Github Discussions](https://github.com/stumpylog/gotenberg-client/discussions/categories/ideas) for feature requests and project improvements. Please check existing discussions before creating a new one to avoid duplicates. |
| 12 | + |
| 13 | +## Bug Reports |
| 14 | + |
| 15 | +If you've identified a bug: |
| 16 | + |
| 17 | +1. Check existing issues to avoid duplicates |
| 18 | +2. Create a new issue using the bug report template |
| 19 | +3. Include: |
| 20 | + - Python version |
| 21 | + - gotenberg-client version |
| 22 | + - Gotenberg server version |
| 23 | + - Minimal code example demonstrating the bug |
| 24 | + - Expected vs actual behavior |
| 25 | + - Error messages/stack traces if applicable |
| 26 | + |
| 27 | +## Development Setup |
| 28 | + |
| 29 | +1. Fork and clone the repository |
| 30 | +1. Install [`uv`](https://astral.sh/uv/) for independent tool installations |
| 31 | + ```bash |
| 32 | + curl -LsSf https://astral.sh/uv/install.sh | sh # Install uv |
| 33 | + ``` |
| 34 | +1. Install [`hatch`](https://github.com/pypa/hatch) and [`pre-commit`](https://github.com/pre-commit/pre-commit) |
| 35 | + ```bash |
| 36 | + uv tool install hatch pre-commit |
| 37 | + ``` |
| 38 | +1. Set up pre-commit hooks: |
| 39 | + ```bash |
| 40 | + pre-commit install |
| 41 | + ``` |
| 42 | + |
| 43 | +## Code Style |
| 44 | + |
| 45 | +We use [`hatch`](https://github.com/pypa/hatch) for project management, testing, and formatting: |
| 46 | + |
| 47 | +- Run tests: `hatch test` |
| 48 | +- Format & lint code: `hatch fmt` |
| 49 | +- Check formatting: `hatch fmt --check` |
| 50 | +- Check typing: `hatch run typing:run` |
| 51 | +- Build documentation: `hatch run docs:build` |
| 52 | + |
| 53 | +Please ensure all tests pass and code is properly formatted before submitting changes. The code must pass the CI to be merged. |
| 54 | + |
| 55 | +## Pull Request Process |
| 56 | + |
| 57 | +1. Create a new branch from `develop` |
| 58 | +2. Make your changes |
| 59 | +3. Update tests and documentation |
| 60 | +4. Run the test suite |
| 61 | +5. Submit a PR against `develop` |
| 62 | +6. Reference any related issues |
| 63 | + |
| 64 | +PRs should: |
| 65 | + |
| 66 | +- Focus on a single feature/fix |
| 67 | +- Include tests for new functionality |
| 68 | +- Update documentation as needed |
| 69 | +- Follow existing code style |
| 70 | + |
| 71 | +## License |
| 72 | + |
| 73 | +By contributing, you agree that your contributions will be licensed under the same terms as the project. |
0 commit comments