@@ -8,9 +8,11 @@ Thank you for your interest in contributing to pySQLY! This document provides gu
88- [ Getting Started] ( #getting-started )
99- [ Development Workflow] ( #development-workflow )
1010- [ Coding Standards] ( #coding-standards )
11+ - [ Documentation] ( #documentation )
1112- [ Testing] ( #testing )
1213- [ Submitting Changes] ( #submitting-changes )
1314- [ Issue Reporting] ( #issue-reporting )
15+ - [ Versioning] ( #versioning )
1416
1517## Code of Conduct
1618
@@ -38,14 +40,12 @@ This project adheres to a [Code of Conduct](CODE_OF_CONDUCT.md) that all contrib
3840 ``` bash
3941 python -m venv venv
4042 source venv/bin/activate # On Windows, use: venv\Scripts\activate
41- pip install -e . # Install in development mode
42- pip install -r requirements.txt
43+ pip install -e " .[dev]" # Install in development mode with development dependencies
4344 ```
4445
45464 . Set up pre-commit hooks:
4647
4748 ``` bash
48- pip install pre-commit
4949 pre-commit install
5050 ```
5151
@@ -84,11 +84,26 @@ pySQLY follows these coding standards:
8484
8585These tools are configured in the project and run automatically with pre-commit hooks.
8686
87+ ### Running the Linters
88+
89+ ``` bash
90+ # Format code with Black
91+ black src/ tests/
92+
93+ # Sort imports with isort
94+ isort src/ tests/
95+
96+ # Lint with Ruff
97+ ruff check src/ tests/
98+ ```
99+
87100## Documentation
88101
89102- Use docstrings for all public modules, functions, classes, and methods
90103- Follow [ Google Style Python Docstrings] ( https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html )
91104- Update documentation when changing functionality
105+ - Add examples for new features
106+ - Keep the [ API Documentation] ( ./API.md ) up to date with any changes
92107
93108## Testing
94109
@@ -120,26 +135,47 @@ pytest --cov=pysqly
120135
1211363 . In your PR description:
122137 - Clearly describe the problem and solution
123- - Include the relevant issue number if applicable
138+ - Include the relevant issue number if applicable (e.g., "Fixes # 123 ")
124139 - Mention if it changes external behavior
140+ - Reference any related PRs or issues
141+
142+ 4 . Wait for the maintainers to review your PR. They may ask for changes before merging.
125143
126144## Issue Reporting
127145
128146- Use the GitHub issue tracker to report bugs or request features
147+ - Before submitting a new issue, check if it already exists
129148- For bugs, include:
130149 - Steps to reproduce
131150 - Expected behavior
132151 - Actual behavior
133152 - Python and pySQLY versions
134153 - Operating system
135154 - Any relevant error messages or logs
155+ - Minimal code example that reproduces the issue
156+
157+ ### Issue Templates
158+
159+ When creating a new issue, choose the appropriate template:
160+
161+ - Bug report: For reporting bugs or unexpected behavior
162+ - Feature request: For suggesting new features or improvements
163+ - Documentation issue: For reporting issues with documentation
136164
137165## Versioning
138166
139167We use [ Semantic Versioning] ( https://semver.org/ ) for version numbers:
140168
141- - MAJOR version for incompatible API changes
142- - MINOR version for backward-compatible new features
143- - PATCH version for backward-compatible bug fixes
169+ - MAJOR version for incompatible API changes (X.0.0)
170+ - MINOR version for backward-compatible new features (0.X.0)
171+ - PATCH version for backward-compatible bug fixes (0.0.X)
172+
173+ ## Related Resources
174+
175+ - [ README] ( ./README.md ) - Project overview
176+ - [ Design Document] ( ./DESIGN.md ) - Architecture and design decisions
177+ - [ Security Policy] ( ./SECURITY.md ) - Security guidelines
178+ - [ Code of Conduct] ( ./CODE_OF_CONDUCT.md ) - Community standards
179+ - [ Changelog] ( ./CHANGELOG.md ) - Version history
144180
145181Thank you for contributing to pySQLY!
0 commit comments